#pipx — Public Fediverse posts

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
"""

#VictronEnergy #SmartSolar #Python #MQTT #HomeAssistent

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

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:

#Linux #Fedora #FedoraLinux

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.

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

Instalarea și utilizarea pipx în Linux

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!

Throughout the years, I switched from #conda -> #pyenv + #poetry -> #uv, and I think I'm finally settling down now. uv made me even ditch #pipx as a global #python tool manager. The #astral folks have done a really superb job 🐍 🦀

Throughout the years, I switched from #conda -> #pyenv + #poetry -> #uv, and I think I'm finally settling down now. uv made me even ditch #pipx as a global #python tool manager. The #astral folks have done a really superb job 🐍 🦀

Throughout the years, I switched from #conda -> #pyenv + #poetry -> #uv, and I think I'm finally settling down now. uv made me even ditch #pipx as a global #python tool manager. The #astral folks have done a really superb job 🐍 🦀

Throughout the years, I switched from #conda -> #pyenv + #poetry -> #uv, and I think I'm finally settling down now. uv made me even ditch #pipx as a global #python tool manager. The #astral folks have done a really superb job 🐍 🦀

Throughout the years, I switched from #conda -> #pyenv + #poetry -> #uv, and I think I'm finally settling down now. uv made me even ditch #pipx as a global #python tool manager. The #astral folks have done a really superb job 🐍 🦀

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!

@[email protected] @[email protected] Если это софтина, а не библиотека то попробуй #pipx https://github.com/pypa/pipx

Я им пользовался, удобно.

@forse

Can you try installing it with `pipx` instead?

pipx will create a Python virtualenv just for that program, and install all of its dependencies into that virtual environment. It can then run independently of any system-level versions of those same packages that are installed *for the distro-shipped Python tools*.

The version pipx installs can be upgraded (or left alone) completely independently of OS updates.

#pip #pipx #virtualenv

An improved method of checking for outdated #pipx packages that excludes dev or alpha packages.

Courtesy of: https://github.com/pypa/pipx/issues/149#issuecomment-2342748206

#python #PackageManagement

Python-Pakete selbst veröffentlichen

In diesem Artikel lernst du, wie du Python-Pakete erstellst, sicher verwaltest und auf PyPI veröffentlichst.

#Python #pip #pipx #pypi.org #Sicherheit #Pakete #Bibliotheken #Skripte #Linux

https://gnulinux.ch/python-pakete-selbst-veröffentlichen

If I remember correctly, I couldn't get a file dependency working like `pipx run` for local development purposes, but the newest version of `uv` seems to work as I would expect.

#Python #PEP723 #uv #pip #pipx

Modern Good Practices for Python Development

An outline of best practices for #Python development, including using tools like #pyenv, #pipx or Development Containers for managing Python versions. It also recommends using pyproject.toml for project configuration, virtual environments for package management, and tools like Black, #Ruff, and #pytest for code formatting, linting, and testing.

#PythonBestPractices #PythonDevelopment #PythonTools #PythonProgramming

https://www.stuartellis.name/articles/python-modern-practices/

Zajęło mi to prawie 3 godziny, ale #PipX 1.6.0 wylądował w #Gentoo, z nową wersją podrobionych danych testowych, które zajmują tylko 70 KiB (autorzy używają ~160 MiB paczek, dla każdej implementacji z osobna).

Co istotniejsze, tym razem nie stworzyłem tego na kolanie, ale napisałem porządny skrypt z instrukcjami, którego będzie można użyć przy kolejnych wersjach.

https://github.com/projg2/pipx-repack-wheels

#Python

It took me almost 3 hours but #PipX 1.6.0 is now in #Gentoo, with an updated test shim that makes it possible to test using fake wheels and is only 70 KiB (vs. upstream that uses ~160 MiB for every single implementation).

What's more important, this time it isn't a handmade proof-of-concept anymore but a proper script with instructions that can be used to easily deal with future releases.

https://github.com/projg2/pipx-repack-wheels

#Python

Man, the longer I have :nixos: #NixOS and :manjaro: #Manjaro running in parallel, the more annoyed I am by the :archlinux: #ArchLinux way, e.g.:

· Python update ⇒ all python-based #AUR packages must be rebuilt. #pipx-installed packages also need reinstallation.
· separation between distro repos and AUR is anoying. 'yay -Syu' (or whatever) never really works in one go (be it some stupid sudo prompt later)
· so many AUR packages don't build reliably or at all.
...

Maybe I was too tired to think properly yesterday. A simple install of the latest #python version (without setting it as the default version) and installing it with #pipx and explicitly setting the python version seemed to work great.

@Tiim

For Ubuntu, the deadsnakes repo can be used to install a bunch of other versions, or the pyenv tool can do it. There are other ways too.

Then, get used to using virtual environments for development (so you're not installing your project's dependencies globally, and you can't get conflicts).

For installing 3rd-party tools not in your OS, i.e. you're not hacking them, just using them, use `#pipx install --python python3.11 <pypi-name>`. pipx is in the system repos.

2/2

#virtualenv

IDK how I can be this late to realise there's 'pipx' for python package management, which is better than the old way of managing python packages 'pip'. I found it really nice that 'pipx' have a feature that allows to run a specific package to try it out before installing it. How comes I only realizing 'pipx' is existing just now 🤯 , like I have been leaving under a rock for years. 😅 🙄

#python #pythonpackages #pip #pipx

IDK how I can be this late to realise there's 'pipx' for python package management, which is better than the old way of managing python packages 'pip'. I found it really nice that 'pipx' have a feature that allows to run a specific package to try it out before installing it. How comes I only realizing 'pipx' is existing just now 🤯 , like I have been leaving under a rock for years. 😅 🙄

#python #pythonpackages #pip #pipx

IDK how I can be this late to realise there's 'pipx' for python package management, which is better than the old way of managing python packages 'pip'. I found it really nice that 'pipx' have a feature that allows to run a specific package to try it out before installing it. How comes I only realizing 'pipx' is existing just now 🤯 , like I have been leaving under a rock for years. 😅 🙄

#python #pythonpackages #pip #pipx

IDK how I can be this late to realise there's 'pipx' for python package management, which is better than the old way of managing python packages 'pip'. I found it really nice that 'pipx' have a feature that allows to run a specific package to try it out before installing it. How comes I only realizing 'pipx' is existing just now 🤯 , like I have been leaving under a rock for years. 😅 🙄

#python #pythonpackages #pip #pipx

IDK how I can be this late to realise there's 'pipx' for python package management, which is better than the old way of managing python packages 'pip'. I found it really nice that 'pipx' have a feature that allows to run a specific package to try it out before installing it. How comes I only realizing 'pipx' is existing just now 🤯 , like I have been leaving under a rock for years. 😅 🙄

#python #pythonpackages #pip #pipx

@tshirtman @diazona @jackwilliambell

Fair enough. I resisted pipenv for quite a while, switched to it for a year or two, and have moved on to poetry with no regrets.

I only use it for projects, though. Personal or work. If I just want to install a Python tool for local use, `pipx` is still just the ticket for it.

#pipx #pipenv #poetry

After upgrading to #ubuntu23.04 I was able to remove all my old venvs and would have a lot to manage if it weren't for #pipx. `pipx reinstall-all` Fixes-Everything™. It even says where command are pointing to some other file than it has setup for you (including broken module callers). Quite awesome. Moving from #python 3.10 to 3.11 has been easier than any move i've ever done before. Thanks pipx!

C'est sympa de pouvoir utiliser la #ligne_de_commande #OpenStack pour gérer les nouveaux #serveurs #GandiCloud #VPS mais ça l'est un peu moins qu'il ne soit (apparemment) pas documenté précisément ce qui est ou n'est pas implémenté par #Gandi. 😅

Et aussi, j'ai installé python-openstackclient avec #pipx plutôt que openstackclient avec pip, contrairement à ce que dit la doc parce que ça me semblait plus propre.