Post #1934015

2026-05-03 17:20 UTC

@stf@chaos.social @slott56@fosstodon.org to be specific 1. install non-system python 2. create virtualenv for your app and install the app-specific libraries in that 3. run your app in an environment that won't change out from under you. As for building python - it's your choice of tool: - pyenv[1] compiles from source - uv[2] downloads a prebuilt binary [1]: https://github.com/pyenv/pyenv [2]: https://github.com/astral-sh/uv

Replies (2)

@stf@chaos.social 2026-05-03 18:18

@hwine@vmst.io @slott56@fosstodon.org i guess my expectations (which i think are low) are like this: packages in a virtualenv are installed in a version independent directory, instead of `env/lib/python3.$minor/site-packages/` simply in `env/lib/python/site-packages` upon upgrading python and running inside the virtualenv: 1. py files run without extra steps 2. pyc files are updated silently if needed 3. .so modules work without changes, if API change in cpython then a warning to reinstall, but works as expected

Open ##1934014
@stf@chaos.social 2026-05-03 17:23

@hwine@vmst.io @slott56@fosstodon.org how about instead of externalising this cost on on thousands of users, just providing a stable lts python that is not requiring all this useless upgrade cycle for nothing?

Open ##2600044