Post #1934019
2026-05-03 14:03 UTC
@slott56@fosstodon.org i don't understand this question. distro rugpulls py3.12 replaces it with py3.13 - virtualenv doesn't find the old binary (and --copy also doesn't work for lack of missing libs), and each binary expects the deps in a versioned directory - so somewhere else - and stuff like uwsgi also cannot find the app any more. the only thing that changes is python.
Replies (2)
-
@stf@chaos.social 2026-05-03 14:06
@slott56@fosstodon.org all i want is stability, i don't want to update any virtualenv just because a new python version is deployed. i don't want to waste my time on this.
-
@slott56@fosstodon.org 2026-05-03 14:57
@stf@chaos.social “distro”? Which distro of what component wrecked an existing Python installation? How did it rug pull the old Python. My installs are always incremental. What specific install rug pulled?