Post #2600045

2026-05-04 01:12 UTC

@stf@chaos.social @slott56@fosstodon.org that's why modern recommendations are to not depend on the system Python, and code to a version you install and control the update cycle of. The newer tooling makes that easy -- if the app is following the conventions. Once your app is using a user installed Python, you never have to update again (which may be fine for a personal app) Depending on the packages you're depending upon, version pinning may help alleviate surprises.

Replies (2)

@stf@chaos.social 2026-05-04 11:03

@hwine@vmst.io @slott56@fosstodon.org i think that is just wrong, i think the interpreter should be stable and not externalize these costs or technical debt on the users. distros are the right way to do it. can you explain me why the modules in `lib/python3.x` cannot be reused over versions? what would break between v3.12 and v3.13 for example? would py, pyc, or .so files break? did the python c api change in a breaking way? and if so why cannot this be done in a gracefully degrading way?

Open ##2600046
@stf@chaos.social 2026-05-04 12:29

@hwine@vmst.io @slott56@fosstodon.org i appreciate you guys trying to help me, but there is a million of similar virtualenvs out there, are you ready to tell all those users that they're all doing it wrong and offering them bandaids and bad workarounds for the deficiencies of the interpreter - and don't tell me it's impossible; we have future, six, - which made the upgrade path bearable. we can have progress without unnecessarily breaking things and wasting users time, with a bit more consideration.

Open ##2600048