#pipx — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #pipx, aggregated by home.social.
-
Wow, pipx now uses Astral's uv as its default backend if it is installed. If it uses uv, then what do I even need pipx for? 😅
To get the old behaviour back, you need to set `PIPX_DEFAULT_BACKEND` to `pip`. The docs consider having uv installed an opt-in to using it by default. 🙈
(edit: clarified)
-
Wow, pipx now uses Astral's uv as its default backend if it is installed. If it uses uv, then what do I even need pipx for? 😅
To get the old behaviour back, you need to set `PIPX_DEFAULT_BACKEND` to `pip`. The docs consider having uv installed an opt-in to using it by default. 🙈
(edit: clarified)
-
Wow, pipx now uses Astral's uv as its default backend if it is installed. If it uses uv, then what do I even need pipx for? 😅
To get the old behaviour back, you need to set `PIPX_DEFAULT_BACKEND` to `pip`. The docs consider having uv installed an opt-in to using it by default. 🙈
(edit: clarified)
-
Wow, pipx now uses Astral's uv as its default backend if it is installed. If it uses uv, then what do I even need pipx for? 😅
To get the old behaviour back, you need to set `PIPX_DEFAULT_BACKEND` to `pip`. The docs consider having uv installed an opt-in to using it by default. 🙈
(edit: clarified)
-
Wow, pipx now uses Astral's uv as its default backend if it is installed. If it uses uv, then what do I even need pipx for? 😅
To get the old behaviour back, you need to set `PIPX_DEFAULT_BACKEND` to `pip`. The docs consider having uv installed an opt-in to using it by default. 🙈
(edit: clarified)
-
RE: https://mamot.fr/@denissalem/116727062417331210
Lately I was complaining about the removal of #pipx from official #gentoo repository. It obviously doesn't disallow me to use #pipx by installing it through #pip …
🤡The removal was certainly justified.
What struck me here is that it is now advised to use #astral_uv in replacement.
Which may be a great software … BUT
But now I need to compile an entire #Rust compiler which is itself a non trivial package for a source based distro …
Does #devs are aware of the concept of #minimalism …?
-
RE: https://mamot.fr/@denissalem/116727062417331210
Lately I was complaining about the removal of #pipx from official #gentoo repository. It obviously doesn't disallow me to use #pipx by installing it through #pip …
🤡The removal was certainly justified.
What struck me here is that it is now advised to use #astral_uv in replacement.
Which may be a great software … BUT
But now I need to compile an entire #Rust compiler which is itself a non trivial package for a source based distro …
Does #devs are aware of the concept of #minimalism …?
-
RE: https://mamot.fr/@denissalem/116727062417331210
Lately I was complaining about the removal of #pipx from official #gentoo repository. It obviously doesn't disallow me to use #pipx by installing it through #pip …
🤡The removal was certainly justified.
What struck me here is that it is now advised to use #astral_uv in replacement.
Which may be a great software … BUT
But now I need to compile an entire #Rust compiler which is itself a non trivial package for a source based distro …
Does #devs are aware of the concept of #minimalism …?
-
RE: https://mamot.fr/@denissalem/116727062417331210
Lately I was complaining about the removal of #pipx from official #gentoo repository. It obviously doesn't disallow me to use #pipx by installing it through #pip …
🤡The removal was certainly justified.
What struck me here is that it is now advised to use #astral_uv in replacement.
Which may be a great software … BUT
But now I need to compile an entire #Rust compiler which is itself a non trivial package for a source based distro …
Does #devs are aware of the concept of #minimalism …?
-
Kinda late but... Whoa, that's harsh. Maybe it's fair. I don't know. What I know is that python package management is still a mess in 2026. This is painful for devs and end users ...
The fact that the current miracle solution comes from #rust is a bit sad since python ecosystem is still unable to have a proper, unified and official package management ...
-
Kinda late but... Whoa, that's harsh. Maybe it's fair. I don't know. What I know is that python package management is still a mess in 2026. This is painful for devs and end users ...
The fact that the current miracle solution comes from #rust is a bit sad since python ecosystem is still unable to have a proper, unified and official package management ...
-
Kinda late but... Whoa, that's harsh. Maybe it's fair. I don't know. What I know is that python package management is still a mess in 2026. This is painful for devs and end users ...
The fact that the current miracle solution comes from #rust is a bit sad since python ecosystem is still unable to have a proper, unified and official package management ...
-
Kinda late but... Whoa, that's harsh. Maybe it's fair. I don't know. What I know is that python package management is still a mess in 2026. This is painful for devs and end users ...
The fact that the current miracle solution comes from #rust is a bit sad since python ecosystem is still unable to have a proper, unified and official package management ...
-
Kinda late but... Whoa, that's harsh. Maybe it's fair. I don't know. What I know is that python package management is still a mess in 2026. This is painful for devs and end users ...
The fact that the current miracle solution comes from #rust is a bit sad since python ecosystem is still unable to have a proper, unified and official package management ...
-
Es gibt eine neue Version von meinem https://github.com/jedie/victron-ble2mqtt Projekt: Hab die vorgeschlagene installation vereinfacht. Nun einfach per #pipx installieren ;)
"""
Emit MQTT events from Victron Energy Solar Charger via victron-ble bluetooth lib
""" -
Es gibt eine neue Version von meinem https://github.com/jedie/victron-ble2mqtt Projekt: Hab die vorgeschlagene installation vereinfacht. Nun einfach per #pipx installieren ;)
"""
Emit MQTT events from Victron Energy Solar Charger via victron-ble bluetooth lib
""" -
Es gibt eine neue Version von meinem https://github.com/jedie/victron-ble2mqtt Projekt: Hab die vorgeschlagene installation vereinfacht. Nun einfach per #pipx installieren ;)
"""
Emit MQTT events from Victron Energy Solar Charger via victron-ble bluetooth lib
""" -
Es gibt eine neue Version von meinem https://github.com/jedie/victron-ble2mqtt Projekt: Hab die vorgeschlagene installation vereinfacht. Nun einfach per #pipx installieren ;)
"""
Emit MQTT events from Victron Energy Solar Charger via victron-ble bluetooth lib
""" -
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
-
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
-
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
-
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
-
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
-
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 :akkosmile2:
-
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 :akkosmile2:
-
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 :akkosmile2:
-
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 :akkosmile2:
-
Not that anyone has asked, or cares, about my podunk, backwater processes. There's a few reasons why I haven't migrated my #Python work to use #uv
1. I don't care about performance. My work is done on a potato machine and it won't make much difference, to me. For now.
2. I prefer to keep the VC funded company Astral at arms length, pay attention, and see how the tool development plays out.
3. I actually like watching individual projects like #pyenv #pipx and the rest. How they work as a community, handle bugs and new features.I did the same with the flake8 module projects before I commited to using ruff several years ago. YMMV
-
Not that anyone has asked, or cares, about my podunk, backwater processes. There's a few reasons why I haven't migrated my #Python work to use #uv
1. I don't care about performance. My work is done on a potato machine and it won't make much difference, to me. For now.
2. I prefer to keep the VC funded company Astral at arms length, pay attention, and see how the tool development plays out.
3. I actually like watching individual projects like #pyenv #pipx and the rest. How they work as a community, handle bugs and new features.I did the same with the flake8 module projects before I commited to using ruff several years ago. YMMV
-
Not that anyone has asked, or cares, about my podunk, backwater processes. There's a few reasons why I haven't migrated my #Python work to use #uv
1. I don't care about performance. My work is done on a potato machine and it won't make much difference, to me. For now.
2. I prefer to keep the VC funded company Astral at arms length, pay attention, and see how the tool development plays out.
3. I actually like watching individual projects like #pyenv #pipx and the rest. How they work as a community, handle bugs and new features.I did the same with the flake8 module projects before I commited to using ruff several years ago. YMMV
-
Not that anyone has asked, or cares, about my podunk, backwater processes. There's a few reasons why I haven't migrated my #Python work to use #uv
1. I don't care about performance. My work is done on a potato machine and it won't make much difference, to me. For now.
2. I prefer to keep the VC funded company Astral at arms length, pay attention, and see how the tool development plays out.
3. I actually like watching individual projects like #pyenv #pipx and the rest. How they work as a community, handle bugs and new features.I did the same with the flake8 module projects before I commited to using ruff several years ago. YMMV
-
Not that anyone has asked, or cares, about my podunk, backwater processes. There's a few reasons why I haven't migrated my #Python work to use #uv
1. I don't care about performance. My work is done on a potato machine and it won't make much difference, to me. For now.
2. I prefer to keep the VC funded company Astral at arms length, pay attention, and see how the tool development plays out.
3. I actually like watching individual projects like #pyenv #pipx and the rest. How they work as a community, handle bugs and new features.I did the same with the flake8 module projects before I commited to using ruff several years ago. YMMV
-
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*
-
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*
-
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*
-
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*
-
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.
-
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.
-
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.
-
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.
-
Instalarea și utilizarea pipx în Linux
Pip este un instrument popular pentru instalarea pachetelor și modulelor Pyton din Python Package Index. Cu toate acestea, în versiunile recente ale distribuțiilor, utilizatorii Pip se confruntă cu un defect de mediu gestionat extern. Aceasta este o „caracteristică” adăugată pentru a evita conflictele dintre pachetele Python instalate prin Pip și managerul de pachete nativ. Python dorește să folosiți medii virtuale separate în loc să instalați pachetul la nivel global […]https://comunitatealinux.ro/instalarea-si-utilizarea-pipx-in-linux/
-
Instalarea și utilizarea pipx în Linux
Pip este un instrument popular pentru instalarea pachetelor și modulelor Pyton din Python Package Index. Cu toate acestea, în versiunile recente ale distribuțiilor, utilizatorii Pip se confruntă cu un defect de mediu gestionat extern. Aceasta este o „caracteristică” adăugată pentru a evita conflictele dintre pachetele Python instalate prin Pip și managerul de pachete nativ. Python dorește să folosiți medii virtuale separate în loc să instalați pachetul la nivel global […]https://comunitatealinux.ro/instalarea-si-utilizarea-pipx-in-linux/
-
Instalarea și utilizarea pipx în Linux
Pip este un instrument popular pentru instalarea pachetelor și modulelor Pyton din Python Package Index. Cu toate acestea, în versiunile recente ale distribuțiilor, utilizatorii Pip se confruntă cu un defect de mediu gestionat extern. Aceasta este o „caracteristică” adăugată pentru a evita conflictele dintre pachetele Python instalate prin Pip și managerul de pachete nativ. Python dorește să folosiți medii virtuale separate în loc să instalați pachetul la nivel global […]https://comunitatealinux.ro/instalarea-si-utilizarea-pipx-in-linux/
-
Instalarea și utilizarea pipx în Linux
Pip este un instrument popular pentru instalarea pachetelor și modulelor Pyton din Python Package Index. Cu toate acestea, în versiunile recente ale distribuțiilor, utilizatorii Pip se confruntă cu un defect de mediu gestionat extern. Aceasta este o „caracteristică” adăugată pentru a evita conflictele dintre pachetele Python instalate prin Pip și managerul de pachete nativ. Python dorește să folosiți medii virtuale separate în loc să instalați pachetul la nivel global […]https://comunitatealinux.ro/instalarea-si-utilizarea-pipx-in-linux/
-
#OpenSUSE in AWS still has python3.6 as system python. Every time I use a python tool and ran into python3.6 and python3.9+ compatibility issues, my heart sinks a little. I know, there are solutions like #uv, #venv, #pipx, #docker, #nix etc!
With #rust you sweat (and cry) during development but with #python (and #js), you sweat (and cry) after deployment!
I'll die on the former hill rather than the later. Thank you!
-
#OpenSUSE in AWS still has python3.6 as system python. Every time I use a python tool and ran into python3.6 and python3.9+ compatibility issues, my heart sinks a little. I know, there are solutions like #uv, #venv, #pipx, #docker, #nix etc!
With #rust you sweat (and cry) during development but with #python (and #js), you sweat (and cry) after deployment!
I'll die on the former hill rather than the later. Thank you!
-
#OpenSUSE in AWS still has python3.6 as system python. Every time I use a python tool and ran into python3.6 and python3.9+ compatibility issues, my heart sinks a little. I know, there are solutions like #uv, #venv, #pipx, #docker, #nix etc!
With #rust you sweat (and cry) during development but with #python (and #js), you sweat (and cry) after deployment!
I'll die on the former hill rather than the later. Thank you!
-
#OpenSUSE in AWS still has python3.6 as system python. Every time I use a python tool and ran into python3.6 and python3.9+ compatibility issues, my heart sinks a little. I know, there are solutions like #uv, #venv, #pipx, #docker, #nix etc!
With #rust you sweat (and cry) during development but with #python (and #js), you sweat (and cry) after deployment!
I'll die on the former hill rather than the later. Thank you!
-
#OpenSUSE in AWS still has python3.6 as system python. Every time I use a python tool and ran into python3.6 and python3.9+ compatibility issues, my heart sinks a little. I know, there are solutions like #uv, #venv, #pipx, #docker, #nix etc!
With #rust you sweat (and cry) during development but with #python (and #js), you sweat (and cry) after deployment!
I'll die on the former hill rather than the later. Thank you!
-
Updating my #Manjaro updated the system's #Python to 3.13, yay!
It broke my #ThonnyIDE which was installed via #pipx, and I'm having torebuild a lot of stuff, not good!
-
Updating my #Manjaro updated the system's #Python to 3.13, yay!
It broke my #ThonnyIDE which was installed via #pipx, and I'm having torebuild a lot of stuff, not good!
-
Updating my #Manjaro updated the system's #Python to 3.13, yay!
It broke my #ThonnyIDE which was installed via #pipx, and I'm having torebuild a lot of stuff, not good!
-
Updating my #Manjaro updated the system's #Python to 3.13, yay!
It broke my #ThonnyIDE which was installed via #pipx, and I'm having torebuild a lot of stuff, not good!
-
Updating my #Manjaro updated the system's #Python to 3.13, yay!
It broke my #ThonnyIDE which was installed via #pipx, and I'm having torebuild a lot of stuff, not good!
