A new blog post by me:

"List outdated packages in Python's pipx without upgrading"

Solving a papercut in pipx with a small bash function.

https://suburbanalities.blogspot.com/2026/03/list-outdated-packages-in-pythons-pipx.html

#Python #pipx #papercut #Blog #Suburbanalities #Bash

Similar to my `uvx add-classifiers` and `uvx add-link` mini projects, recently made a `uvx set-license` to simplify that step of setting up new projects.
https://pypi.org/project/set-license/
https://codeberg.org/kfdm/set-license

Light wrapper around https://api.github.com/licenses to add the `license` line to `pyproject.toml` and write to `LICENSE.md`
#python #uvx #pipx

Well, the upgrade to #Fedora43 was almost uneventful. There was a minor issue with #wine, but everything went well after I uninstalled and reinstalled it.

Some font options were reset to the default, so everything looked "too big" after rebooting. I also had to reinstall all my #pipx packages. But that's it.

I could have waited a couple of weeks to upgrade, but I thought, "Meh, whatever, it's not #Windows." and went ahead  

#Linux #Fedora #FedoraLinux

Huh. This is a new one.

Somehow, I've managed to pollute my #Python pip userspace with a bunch of packages from a #Poetry project I normally work on.

Fortunately, I could just easily rebuild with #pyenv and #pipx. Just kinda weird that it happened in the first place. I might have to go back to explicitly using `poetry shell` for isolation. *shrug*

Just a little note for anyone interested...

Running ```pip-audit``` revealed a #vulnerability in pip25.2 with no #PyPI database update available yet.

The immediate fix is a manual patch update to pip 25.3.dev0 - #Development version.

#python #python3 #pip #pip3 #pipx #security

Took another swing at upgrading from #debian #bookworm to #trixie.
apt-upgrade --without-new-pkgs done first, then normal apt upgrade, then apt dist-upgrade.

Checked #udd for bugs etc, plus a quick re-read of the release notes.

This time things worked better, because I fixed some sources before the upgrade and removed a couple of things I'd gotten from deb-multimedia which had compromised certain aspects of the upgrade last time I tried.

Mostly painless, and all working. I've stuck with #xfce for the desktop, at least for now whilst testing #kde in a VM.

I had to do a 'pipx reinstall-all' to fix the underlying #python in those virtual environments.

And had to do #python virtual environment upgrades in my normal venv folders for the handful of things I run that don't seem to like #pipx

All done and will now monitor and record any issues, and raise bugs if I get anything serious. But I doubt anything will be a problem given the imminent release of #trixie in the next 6 to 8 weeks.

It turned out that I've found a all-in-one replacement for #pip, #pipx and other #python package manegers.

https://docs.astral.sh/uv/

Spent the evening upgrading from #debian #bookworm as the current stable to #trixie (which is still testing but is now well into freeze, so little will change for everyday use).

Checked the draft release notes and did the inline upgrade. Mostly okay.

Annoyances were from having to set up virtual environments again for #python apps. I tend to use #pipx and couldn't just do an upgrade, I had to refresh the #python runtime within each #pipx venv. Bit annoying, but not too onerous.

Main issue stems from a couple of apps that are not in the #debian repos.
#dvbcut hasn't been updated to be #trixie compliant, and that isn't available as #appimage or #flatpak, so that will be something I'll lose until I can sort out a docker or VM to run it if I truly need it still.
Other was trying to get #avidemux to compile and run - several fruitless hours later, and that isn't working either. For now I've gone with the flatpak but it's not official and I don't really like flatpaks if I can avoid them.

Instalarea și utilizarea pipx în Linux

https://comunitatealinux.ro/instalarea-si-utilizarea-pipx-in-linux/