fi cient software. • Let's not kid ourselves: it's bloody complicated • Yet as a programmer you're surprisingly productive with it • The ecosystem has excellent DX • The language values backwards compatibility • The language values innovation and progress
painful • Downloading the compiler/interpreter doesn't have to be painful • Switching between compiler/interpreter versions can be trivial • One can have the same experience on Linux, macOS, and Windows
Rye's stewardship to Astral • uv — today — is a replacement for pip-tools/pip/venv • uv tomorrow will fully replace the need of Rye by absorbing it in spirit
Where do you store dependency attached meta information? • Impossible to encode even more into these strings without breaking already existing tools • Who can write these strings?
Pick the right index (PyPI vs internal) • Git checkout, local paths, multi-version matches • Tool speci fi c proprietary (even if only temporary) extra information
idea • Already countless of proprietary extensions by di ff erent tools • Many di ff erent ways to de fi ne licenses • Complex resolutions caused by markers
1 • How can you ever fi nd a solution? • Rust/Node: permits multi-version resolutions • Issues: sys.modules (though solvable), C-extension modules (CABI)
standard format for distributing Python Binaries • indygreg builds are great, but have portability issues (bad CFLAGS, missing readline, …) • Not an o ff i cial project, run by a single person