Testing & Packaging

Everything you need to know today about Python Packaging: PEPs 517/518, pyproject.toml, Pipenv, setuptools, and—of course—pip.

I make Python packages for everything. Big projects obviously get a package, but so does every tiny analysis. Spinning up a quick jupyter notebook to check something out? Build a package first. Oh yeah, and every package gets its own virtual environment. Let’s back up a little bit so that I can tell you why I do this. After that, I’ll show you how I do this. Notably, my workflow is set up to make it simple to stay consistent.

Python Learning materials HSF training curriculum (Python, bash, git, docker, and more) Topical articles CPython core developers Brett Cannon is a CPython core developer, and is very interested in standardizing packaging. https://snarky.ca Why I don’t like SemVer anymore: A great resource to make you think about what SemVer means and where it falls short. What the heck is pyproject.toml: A intro to modern Python packaging A quick-and-dirty guide on how to install packages for Python: This showw the “correct” way to throw together packages (pre-pipx). Paul Ganssle is CPython core developer, and maintains zoneinfo. https://blog.ganssle.io

A guide to modern Python tooling with a focus on simplicity and minimalism.

Thoughts on packaging python libraries — Note This is about packaging libraries, not applications. ⸻ All the advice here is implemented in a project template (with full support for C...

In this step-by-step tutorial, you’ll learn how to create a Python package for your project and how to publish it to PyPI, the Python Package Repository. Quickly get up to speed on everything from naming your package to configuring it using setup.cfg.