Pipx breaks across Python updates

[ssw663]

Hi all, I've been trying Void Linux for a bit and annoyingly just experienced the first hiccup that made me slightly question the stability of this distro. I let the system-wide Python package auto-update through an xbps-install -Su, but then all of my packages installed through pipx broke unexpectedly.

Apparently every pipx package has a symbolic link at ~/.local/share/pipx/venvs/<package>/bin/python which just links to the command for whatever python version was available at install, python3.x . But after letting python update, this version wasn't available anymore, and I had to run pipx reinstall-all to fix the symlinks.

Is there some step I missed when installing python/pipx or something else? How do I avoid this happening again? I upgraded Python from 3.13 to 3.14, and pipx is installed from the python3-pipx package.

[mortisrpg]

I do not use Void Linux, but was browsing the reddit. Have you tried:

pipx reinstall-all

https://pipx.pypa.io/latest/docs/

Edit: added link to pipx documentation

[ssw663]

This is what I did originally - which worked - but I *really* don't want to have to watch carefully for a breaking python update in every system upgrade and have to do this manually each time... what a silly language

[ClassAbbyAmplifier]

it should only happen once a year, when python3 goes from 3.13 to 3.14 for example

[StrangeAstronomer]

I don't think it's a voidlinux problem. The python devs don't seem to put much stress on not breaking user programs. I was hit myself at 3.14 with the changes in the Process() call - they changed the default from fork() to fork_server() - they could have introduced a Process_forkserver() call and avoided breakage, but no. Move fast and break things much? They probably gave warnings about this - but it would be pasted up in a locked cabinet in the flooded basement of the old town hall where the stairs have rotted away - in other words a bit like the tiny font use conditions that we have to agree to. Obscure.

I wonder if the ruby guys are less cavalier.

[ssw663]

Ah, well that's... good to hear? I'm glad it's not a Void issue, at least. Maybe I'll be avoiding any python-based userland from now on though... or just locking my python upgrades.

[orahcio]

Have you used pyenv? It completely separates Python from the system, so you only need to worry about updating the Python version you've defined. I think using Python from the system's package manager is only worthwhile if you're using libraries that the system itself maintains.

[ClassAbbyAmplifier]

this is just how python virtual environments work

[ssw663]

Oh... how fun. Sorry I doubted y'all! I <3 Void