thank you for writing in. Most probably, this is just a documentation flaw. We only recently changed the documentation to use pipx instead of pip[1], and apparently slapped the --upgrade option on it, before validating it beforehand. Apologies.
We submitted a fix right away [2], thanks a stack for making us aware about that problem.
You are right.
Issuing the command without “–upgrade” works
root@0b4f08cecea9:/# pipx install crash
installed package crash 0.31.5, installed using Python 3.11.2
These apps are now globally available
- crash
done! ✨ 🌟 ✨
root@0b4f08cecea9:/# crash --version
0.31.5
root@0b4f08cecea9:/#
BTW I saw that in Debian stable pipx is at 1.1.0 version; bu on github the latest version is 1.7.1
I was not able to upgrade pipx in Debian.
Maybe you can specify a minimal pipx version?
Thank you for letting us know. Unless there are specific problems with pipx, I don’t think we need to specify a minimal version. [1]
With kind regards,
Andreas.
NB: Please let us know about anything we can improve. It is much appreciated, and we love your attention to details.
With Debian, it is well-known that they are opting for stability instead of freshness, which is not a bad thing. Please note because pipx is provided by the operating system vendor, it is not advisable to upgrade it out-of-band. ↩︎