This is adapted from my “Better developers” newsletter: https://BetterDevelopersWeekly.com. Like many others in the Python world, I’ve adopted “uv“, the do-everything, lightning-fast package manager written in Rust. uv does it all: For people who just want to download and install packages, it replaces pip. For people who want to keep multiple versions of Python on […]| Reuven Lerner
This PEP proposes a new file format for specifying dependencies to enable reproducible installation in a Python environment. The format is designed to be human-readable and machine-generated. Installers consuming the file should be able to calculate wha...| Python Enhancement Proposals (PEPs)
This PEP proposes extending the core metadata specification for Python packaging to include a new, repeatable field named Import-Name to record the import names that a project owns once installed. A new key named import-names will be added to the [proje...| Python Enhancement Proposals (PEPs)
Managing dependencies| docs.astral.sh
Specification¶| packaging.python.org
yY6 xj7Y`Û = xj7Y`Û W zU7hE5ÈÁ| oxidase.github.io
After signing up for GitHub Sponsors, I had a nagging feeling that somehow asking for money from other people to support my open source work was inappropriate. But after much reflection, I realized that phrasing the use of GitHub Sponsors as a way to express patronage/support and appreciation for| Tall, Snarky Canadian
The pyproject.toml file In package mode, the only required fields are name and version (either in the project section or in the tool.poetry section). Other fields are optional. In non-package mode, the name and version fields are required if using the project section. Note Run poetry check to print warnings about deprecated fields. The project section The project section of the pyproject.toml file according to the specification of the PyPA. name The name of the package. Always required when t...| python-poetry.org
Two years since PEP 665 was rejected and three years since I started working towards some lock file solution, I present my next (and last regardless of outcome) attempt at coming up with a lock file standard. Terms “platform”: OS plus CPU “environment”: interpreter plus platform “distribution”: in the PyPA spec sense, i.e. a project “lock entry”: a set of distribution files locked for a specific environment “lock file”: a set of lock entries for a specific set of dependenc...| Discussions on Python.org
Description¶| pip.pypa.io
Binary Distribution¶A specific kind of Built Distribution that contains compiled| packaging.python.org
Description¶| pip.pypa.io