Post #1934014
2026-05-03 18:18 UTC
@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
Replies (2)
-
@hwine@vmst.io 2026-05-04 00:46
@stf@chaos.social @slott56@fosstodon.org we're starting to get into specifics of your app, especially since you're mentioning .so files. IF the packages you require are on PyPI AND your app uses "pyproject.toml ", then what you want should work with "uv". If your app does not meet those requirements, it may not be supported out-of-the-box. (I am not familiar with all the packaging variations, so I think it's worth trying uv in case it does support it.)
-
@slott56@fosstodon.org 2026-05-03 22:17
@stf@chaos.social @hwine@vmst.io the packages can’t be in a version-independent directory. Too many packages have version-specific features.