[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#916261: RFP: python-pipx -- Execute binaries from Python packages in isolated environments



Package: wnpp
Severity: wishlist

* Package name    : python-pipx
  Version         : 0.10.3.0
  Upstream Author : Chad Smith <chad@grassfedcode.com>
* URL             : https://github.com/cs01/pipx
* License         : MIT
  Programming Lang: Python
  Description     : Execute binaries from Python packages in isolated environments

pipx allows you to

* Run the latest version of a CLI application from a package in a temporary virtual environment, leaving your system untouched after it finishes
* Install packages to isolated virtual environments, while globally exposing their CLI applications so you can run them from anywhere
* Easily list, upgrade, and uninstall packages that were installed with pipx
* Run with regular user permissions, never calling `sudo pip install` ... (you aren't doing that, are you? 😄).

pipx is a utility similar to pipsi and npx. You could achieve the same result with `pip install --local MYPACKAGE` but all executables installed that way share dependencies, and may have conflicting dependencies. By contrast, pipx creates isolated virtualenvs for each utility. You can achieve the same result with `pipsi install MYPACKAGE` but pipsi appears to be unmaintained and lacks useful features compared to pipx (and is unlikely to get them). See https://github.com/cs01/pipx#how-does-this-compare-to-pipsi for details. This utility would additionally benefit from native packaging to leapfrog the installation conundrum, "what tool do I use to install pipx itself?" See https://github.com/cs01/pipx/issues/44 for details.

Reply to: