How do I get a Python command-line tool onto my machine without it fighting other tools' dependencies?

it builds a dedicated environment for that package and installs it there, so nothing it depends on can collide with another tool's or the system interpreter's packages | it exposes the package's entry points on the user's PATH afterward, so the command just runs

Which command-line tools have I installed this way, and are any of them out of date?

it keeps a record of everything installed through it and can list them all, checking each against the latest published version to flag ones with upgrades available

How do I try a Python tool once without leaving anything behind on this machine?

it builds a throwaway environment, runs the requested command in it, and discards the environment afterward, so nothing is left installed

Can I run a tool with an extra plugin or dependency it doesn't normally ship with?

it lets you name additional packages to install alongside the target inside the same temporary or installed environment, so a plugin that isn't bundled is still available at run time

Will installing or updating one tool ever break the dependencies of another tool I've installed?

each package lives in its own environment rather than a shared one, and uninstalling or upgrading one only touches its own environment, leaving the others untouched

What would changing my shell setup to add this tool's commands actually do to my PATH before I commit to it?

it can report which directories it would add to PATH without writing to PATH or any shell configuration file, so the effect is visible beforehand

python-pipx release history — The Cyber Toolchain

docs update Oct 18, 2026 · issue 112

pipx gains PIPX_COOLDOWN env var, parallel multi-venv operations, lazy imports on Python 3.15, and pipx upgrade-shared command⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Set a global release-age cooldown so pipx skips reinstalling any package updated within the last 7 days, across every install and upgrade command.

$ export PIPX_COOLDOWN=7d
pipx upgrade-all

Force-refresh the shared pip immediately without waiting for the 30-day automatic cycle.

$ pipx upgrade-shared

Opt out of lazy imports on Python 3.15 if a tool relies on eager module initialization at startup.

$ export PYTHON_LAZY_IMPORTS=normal
pipx install mytool

Adds PIPX_COOLDOWN environment variable as a default --cooldown value for install, install-all, inject, upgrade, upgrade-all, and run, so a single release-age policy covers every command; --cooldown 0 opts a single command out.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds pipx upgrade-shared command to manually refresh shared pip ahead of the 30-day automatic refresh cycle.
Defers every import, including dependencies, on Python 3.15 for faster startup; set PYTHON_LAZY_IMPORTS=normal to opt out.
Translates recorded index options when install-all --backend switches between pip and uv backends.
Puts --suffix last in app names (before any Windows file extension), changing how apps exposed by 1.17.14 are renamed on next expose.

+1 more show less

upgrade and reinstall-all now refresh shared pip only after 30 days instead of on every run.

Adds PIPX_COOLDOWN environment variable as a default --cooldown value for install, install-all, inject, upgrade, upgrade-all, and run, so a single release-age policy covers every command; --cooldown 0 opts a single command out.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds pipx upgrade-shared command to manually refresh shared pip ahead of the 30-day automatic refresh cycle.

4 more in Everything

└──▷ BREAKING ON UPGRADE

!Apps exposed by pipx 1.17.14 with --suffix keep their old name until pipx next exposes them, at which point they are renamed to place the suffix last (before any Windows file extension).
!pipx run cache keys have changed; existing cached environments from before the 2026-09-28 fix are incompatible — run pipx cache purge to remove old entries.
!Existing pipx manifest lock locks record the wrong default dependency group; run pipx manifest lock again to fix them.
!PIPX_MAX_LOGS=0 now prunes all log files instead of keeping all of them.

docs update Oct 18, 2026 · issue 112

pipx now documents private index, proxy, and offline install support via --index-url, --pip-args, and PIP_* env vars⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Install a private package from an authenticated internal index in a CI pipeline where the index is not PyPI.

$ pipx install my-package --index-url https://my-index.example.com/simple/ --pip-args="--trusted-host my-index.example.com"

Install packages completely offline from a pre-downloaded wheel directory, bypassing any network calls including shared-library upgrades.

$ pipx install my-package --pip-args="--no-index --find-links /path/to/wheels" --skip-maintenance

Set a private index permanently for all pipx commands in a shell session or profile so every install, inject, and upgrade uses your internal registry.

$ export PIP_INDEX_URL=https://my-index.example.com/simple/
export PIP_TRUSTED_HOST=my-index.example.com
pipx install my-private-package

Supports --index-url directly on any pipx install command to pull packages from a private or self-hosted PyPI index.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Forwards arbitrary pip flags via --pip-args on pipx install, including --extra-index-url, --trusted-host, --no-index, and --find-links for offline wheel directories.
Forwards PIP_* environment variables (e.g. PIP_INDEX_URL, PIP_TRUSTED_HOST) to every pip invocation, including shared-library upgrades, when using the pip backend.
Supports UV_INDEX_URL and other uv-native variables when using the uv backend, since PIP_* variables are ignored by uv.
Adds --skip-maintenance flag to pipx install to retain the bundled pip and avoid network calls during shared-library upgrades in offline scenarios.

+2 more show less

Under the uv backend, pipx run translates a documented subset of --pip-args: --index-url (-i), --extra-index-url, --find-links (-f), --trusted-host, --no-binary, --only-binary, --pre, --upgrade (-U), and --no-cache-dir; any other flag raises an error.
pipx always sets PIP_USER=0 and drops PIP_TARGET so packages are installed into the venv rather than the user site.

Supports --index-url directly on any pipx install command to pull packages from a private or self-hosted PyPI index.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Forwards arbitrary pip flags via --pip-args on pipx install, including --extra-index-url, --trusted-host, --no-index, and --find-links for offline wheel directories.
Forwards PIP_* environment variables (e.g. PIP_INDEX_URL, PIP_TRUSTED_HOST) to every pip invocation, including shared-library upgrades, when using the pip backend.
Supports UV_INDEX_URL and other uv-native variables when using the uv backend, since PIP_* variables are ignored by uv.
Adds --skip-maintenance flag to pipx install to retain the bundled pip and avoid network calls during shared-library upgrades in offline scenarios.

2 more in Everything

docs update Oct 18, 2026 · issue 112

pipx gains dependency cooldown via --cooldown and PIPX_COOLDOWN to skip index artifacts uploaded too recently⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Protect a single install from a supply-chain incident by skipping packages uploaded in the last 7 days.

$ pipx install --cooldown 7 httpie

Apply a machine-wide cooldown so every pipx install and upgrade silently skips too-recent releases — add to your shell profile to persist across sessions.

$ export PIPX_COOLDOWN=7
pipx upgrade-all

Verify the cooldown value recorded in a specific environment's metadata after install.

$ pipx list --output json | jq '.venvs.httpie.metadata.main_package.cooldown_days'

Adds --cooldown DAYS flag to install, install-all, inject, upgrade, upgrade-all, and run to skip index artifacts uploaded within the given number of days, giving compromised or broken releases time to be yanked.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds PIPX_COOLDOWN environment variable to apply a machine-wide cooldown to all supported commands without passing the flag each time.
Translates the cooldown policy for both pip (via --uploaded-prior-to P7D) and uv (via --exclude-newer P7D) automatically.
Stores the effective cooldown_days value in each environment's metadata, readable via pipx list --output json.
Passing --cooldown together with --lock errors immediately, while PIPX_COOLDOWN is silently ignored when a pylock.toml is present.

5 details in Everything

docs update Oct 18, 2026 · issue 112

pipx gains --fetch-python and PIPX_FETCH_PYTHON to auto-download standalone Python builds when the system interpreter is missing or broken.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Install an app under a downloaded standalone Python when the system is missing the required version — ideal for CI runners or distros that strip modules like tkinter or lzma.

$ pipx install --python 3.12 --fetch-python=missing my-package

Pin every install in a CI job to a standalone build regardless of what Python the runner provides, then verify which interpreter was selected.

$ export PIPX_FETCH_PYTHON=always
pipx install --python 3.11 my-package
pipx list

After accumulating several standalone builds, update all their patch releases and remove stale ones.

$ pipx interpreter upgrade
pipx interpreter prune
pipx interpreter list

Adds --fetch-python flag (values: never, missing, always) to pipx install to control whether a standalone Python build is downloaded from python-build-standalone when no local interpreter satisfies the app's requires-python.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds PIPX_FETCH_PYTHON environment variable accepting the same never/missing/always values to set the fetch policy for an entire shell session.
Adds pipx interpreter list, pipx interpreter prune, and pipx interpreter upgrade subcommands to manage cached standalone Python interpreters.

3 details in Everything

└──▷ BREAKING ON UPGRADE

!--fetch-missing-python and PIPX_FETCH_MISSING_PYTHON are deprecated aliases for --fetch-python=missing / PIPX_FETCH_PYTHON=missing; pipx now errors if both PIPX_FETCH_MISSING_PYTHON and PIPX_FETCH_PYTHON are set simultaneously.

docs update Oct 18, 2026 · issue 112

pipx now auto-links shell completions for installed apps via PIPX_COMPLETION_DIR, covering bash, fish, and zsh⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Enable tab completion for pipx subcommands in your current shell.

$ pipx completions

Configure zsh to load completions for pipx-installed apps by adding the pipx completion directory to fpath before compinit.

$ fpath+=("$(pipx environment --value PIPX_COMPLETION_DIR)/zsh/site-functions")

Adds PIPX_COMPLETION_DIR (default ~/.local/share) to control where pipx links completion scripts shipped by installed packages, with subdirectories for bash (bash-completion/completions/), fish (fish/vendor_completions.d/), and zsh (zsh/site-functions/).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds pipx completions command to print shell-specific setup instructions for enabling pipx tab completion.
Adds pipx environment --value PIPX_COMPLETION_DIR to retrieve the active completion directory path, needed for zsh fpath configuration.
Completions installed with a package are automatically removed by pipx uninstall, or removed without uninstalling via pipx unexpose.

4 details in Everything

docs update Oct 18, 2026 · issue 112

pipx gains --global, --prepend, --dry-run, --skip-maintenance, and --value flags plus new env-var overrides for system-wide and custom-path installs.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Install a tool system-wide so all users on the machine can run it.

$ sudo pipx install --global pycowsay

Preview which PATH entries ensurepath would add before committing any changes to shell config files.

$ pipx ensurepath --dry-run

Confirm exactly which directory pipx will use for environments after setting a custom PIPX_HOME.

$ PIPX_HOME=/data/pipx pipx environment --value PIPX_HOME

Adds a --global flag that can follow any subcommand (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ pipx install --global, pipx list --global) to operate on the system-wide installation at /opt/pipx, /usr/local/bin, /usr/local/share/man, and /usr/local/share; adds PIPX_GLOBAL_HOME, PIPX_GLOBAL_BIN_DIR, PIPX_GLOBAL_MAN_DIR, and PIPX_GLOBAL_COMPLETION_DIR environment variables to override those default global paths; and adds sudo pipx ensurepath --global to write the global binary directory to PATH system-wide, creating /etc/profile.d/pipx.sh on Linux or /etc/paths.d/pipx on macOS.
Adds PIPX_MAN_DIR and PIPX_COMPLETION_DIR environment variables (defaulting to ~/.local/share/man and ~/.local/share) alongside the existing PIPX_HOME and PIPX_BIN_DIR to control per-user install locations.
Adds --value argument to pipx environment (e.g. pipx environment --value PIPX_HOME) to print the resolved path for a single variable, reflecting any active override.
Adds a --prepend flag to pipx ensurepath to prepend the pipx bin directory to PATH instead of appending it, so pipx-installed binaries take precedence over system binaries of the same name, and a --dry-run flag to report which directories would be added to PATH without modifying any shell configuration file.
Adds a PIPX_DISABLE_SHARED_LIBS_AUTO_UPGRADE=1 environment variable to skip automatic shared-library upgrades during commands such as pipx install and pipx upgrade, and a --skip-maintenance flag to suppress automatic shared-library upgrades for a single command without setting the global env variable.

Adds a --global flag that can follow any subcommand (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ pipx install --global, pipx list --global) to operate on the system-wide installation at /opt/pipx, /usr/local/bin, /usr/local/share/man, and /usr/local/share; adds PIPX_GLOBAL_HOME, PIPX_GLOBAL_BIN_DIR, PIPX_GLOBAL_MAN_DIR, and PIPX_GLOBAL_COMPLETION_DIR environment variables to override those default global paths; and adds sudo pipx ensurepath --global to write the global binary directory to PATH system-wide, creating /etc/profile.d/pipx.sh on Linux or /etc/paths.d/pipx on macOS.
Adds --value argument to pipx environment (e.g. pipx environment --value PIPX_HOME) to print the resolved path for a single variable, reflecting any active override.
Adds a PIPX_DISABLE_SHARED_LIBS_AUTO_UPGRADE=1 environment variable to skip automatic shared-library upgrades during commands such as pipx install and pipx upgrade, and a --skip-maintenance flag to suppress automatic shared-library upgrades for a single command without setting the global env variable.

2 more in Everything

└──▷ BREAKING ON UPGRADE

!After version 1.16.0, default paths moved from ~/.local/pipx to per-platform directories via platformdirs (e.g. ~/.local/share/pipx on Linux); existing installations at ~/.local/pipx are preserved for compatibility, but new installs use the new layout.

docs update Oct 18, 2026 · issue 112

pipx gains a pipx manifest command and pipx.toml file for declarative, lock-file-backed tool management⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Declare and pin every team tool in one pipx.toml, then generate PEP 751 lock files so every developer installs identical artifacts.

$ pipx install nab
pipx manifest lock ./pipx.toml

Bootstrap or update all declared tools on a fresh machine (and remove any stale envs not in the manifest) using a pre-locked manifest.

$ pipx manifest sync ./pipx.toml --prune

Define a pipx.toml that pins two tools, one with a lock file and one floating, ready for pipx manifest sync.

pipx.toml

[project]
name = "pipx-tools"
version = "1"
dependencies = []
requires-python = ">=3.10"

[dependency-groups]
black = ["black>=25,<26"]
httpie = ["httpie"]

[tool.pipx]
version = "1.0"

[tool.pipx.tools.black]
apps = ["black"]
lock = "pylock.black.toml"

[tool.pipx.tools.httpie]
apps = ["http", "https"]

Adds pipx manifest subcommand to install, upgrade, or prune a declared set of tools as a unit from a pipx.toml manifest file, including pipx manifest lock ./pipx.toml to resolve each locked dependency group into a PEP 751 lock file via nab, and pipx manifest sync ./pipx.toml to install, upgrade, or downgrade every declared tool, resolving unlocked specs or installing from named PEP 751 lock files.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds --prune flag to pipx manifest sync to uninstall pipx environments absent from the manifest, plus --global and --backend options to select the pipx store or installation backend.
Adds pipx.toml manifest format using [dependency-groups] for PEP 508 package requirements and [tool.pipx.tools.<name>] tables for per-tool policy including suffix, apps, include-dependencies, include-resources-from, expose, and lock keys; the lock key declares a relative PEP 751 lock file path, seeding existing locks into replacements and writing atomically only after all resolutions succeed; the suffix key installs multiple versions of the same tool side-by-side using the normalized package name plus suffix as the environment name; and the include-resources-from key selects dependency resources from a named package without combining with include-dependencies.

3 details in Everything

docs update Oct 18, 2026 · issue 112

pipx gains expose, unexpose, and --include-resources-from to control which apps, man pages, and completions reach PATH.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Hide a globally installed tool from PATH when a system version should take precedence, without removing the pipx environment.

$ pipx unexpose ansible

Expose only the tox-to-nox converter shipped by one dependency rather than pulling every dependency's apps onto PATH.

$ pipx install "nox[tox_to_nox]" --include-resources-from tox

Re-link a manually deleted app symlink without reinstalling the environment.

$ pipx expose ansible

Adds pipx unexpose <app> to hide an app, manual pages, and shell completions from PATH without rebuilding the environment; the hidden state survives upgrades, reinstalls, and injected packages.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds pipx expose <app> to restore missing symlinks for apps, manual pages, and shell completions without rebuilding the environment, leaving files pipx does not own in place.
Adds --include-resources-from <PACKAGE> flag to pipx install and pipx inject to selectively expose apps, manual pages, and shell completions from a single named dependency; repeatable for multiple packages.
Extends --include-deps on pipx install to expose apps and manual pages from every dependency in the environment.

Adds pipx unexpose <app> to hide an app, manual pages, and shell completions from PATH without rebuilding the environment; the hidden state survives upgrades, reinstalls, and injected packages.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds pipx expose <app> to restore missing symlinks for apps, manual pages, and shell completions without rebuilding the environment, leaving files pipx does not own in place.
Adds --include-resources-from <PACKAGE> flag to pipx install and pipx inject to selectively expose apps, manual pages, and shell completions from a single named dependency; repeatable for multiple packages.

1 more in Everything

└──▷ BREAKING ON UPGRADE

!--include-apps-from is renamed to --include-resources-from; the old name is still read from metadata written by earlier versions but new invocations should use --include-resources-from.

docs update Oct 18, 2026 · issue 112

pipx gains pin/unpin commands to hold environments at fixed versions and skip them during upgrades.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Lock a tool at its current version so routine pipx upgrade-all runs never touch it.

$ pipx pin black

Audit all currently pinned environments from a script by consuming structured output.

$ pipx list --pinned --include-injected

Adds pipx pin PACKAGE command to pin the main package and all injected packages in an environment, causing pipx upgrade and pipx upgrade-all to skip it.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds pipx pin PACKAGE --injected-only to leave the main package upgradable while pinning every injected package.
Adds pipx pin PACKAGE --skip PKG_A PKG_B to pin injected packages except the listed ones (implies --injected-only).
Adds pipx unpin PACKAGE to unpin the main package and every pinned injected package in that environment.
Adds --output json and --quiet flags to pipx pin/pipx unpin for scripted consumption of changed and skipped packages.

+3 more show less

Adds pipx list --pinned to list pinned environments, with --include-injected to also show pinned injected packages.
pipx reinstall refuses a pinned environment; pipx reinstall-all reports it as an error.
pipx install --force and pipx inject --force preserve a package's pinned state even when installing a different version.

Adds pipx pin PACKAGE command to pin the main package and all injected packages in an environment, causing pipx upgrade and pipx upgrade-all to skip it.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds pipx pin PACKAGE --injected-only to leave the main package upgradable while pinning every injected package.
Adds pipx pin PACKAGE --skip PKG_A PKG_B to pin injected packages except the listed ones (implies --injected-only).
Adds pipx unpin PACKAGE to unpin the main package and every pinned injected package in that environment.
Adds --output json and --quiet flags to pipx pin/pipx unpin for scripted consumption of changed and skipped packages.

+2 more show less

Adds pipx list --pinned to list pinned environments, with --include-injected to also show pinned injected packages.
pipx reinstall refuses a pinned environment; pipx reinstall-all reports it as an error.

1 more in Everything

docs update Oct 18, 2026 · issue 112

python-pipx: Adds --output json flag to pipx inject and pipx uninject to return a versioned result envelope in JSON.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Inject multiple packages from a requirements file into an existing pipx environment in one shot — useful for reproducible dev setups.

$ pipx inject ipython -r useful-packages.txt

Expose only the browser apps from a single dependency after injecting a large framework, without pulling every dependency's entry points into PATH.

$ pipx inject robotframework-keyta robotframework-browser-batteries --include-resources-from robotframework-browser

Inspect which packages have been injected under each managed environment to audit your pipx setup.

$ pipx list --include-injected

Adds -r <file> flag to pipx inject to inject packages from a requirements file (e.g. pipx inject ipython -r useful-packages.txt).
Adds --with-suffix flag to pipx inject to give injected package apps the host environment's suffix (e.g. injecting black into ipython_3.11 exposes black_3.11).
Adds --editable / -e flag to pipx inject to install a package in editable (development) mode.
Adds --force / -f flag to pipx inject to reinstall a package even when it is already injected.
Adds --index-url / -i flag to pipx inject to set the package index URL for a specific inject operation.

+2 more show less

Adds --pip-args flag to pipx inject to pass extra arguments directly to pip (e.g. --pip-args='--no-cache-dir').
Adds --include-injected flag to pipx list to display injected packages under their host environment.

Adds -r <file> flag to pipx inject to inject packages from a requirements file (e.g. pipx inject ipython -r useful-packages.txt).
Adds --with-suffix flag to pipx inject to give injected package apps the host environment's suffix (e.g. injecting black into ipython_3.11 exposes black_3.11).
Adds --editable / -e flag to pipx inject to install a package in editable (development) mode.
Adds --index-url / -i flag to pipx inject to set the package index URL for a specific inject operation.
Adds --pip-args flag to pipx inject to pass extra arguments directly to pip (e.g. --pip-args='--no-cache-dir').

+1 more show less

Adds --include-injected flag to pipx list to display injected packages under their host environment.

1 more in Everything

1.18.2 Oct 16, 2026 · issue 110

pipx 1.18.2 adds support for absolute file URLs when installing local packages.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION

$ git clone --branch 1.18.2 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.18.2

└──▷ TRY IT

Install a locally built wheel or source tree using an absolute file URL instead of a bare path.

$ pipx install file:///home/user/projects/mytool

Supports absolute file URLs (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ file:///path/to/package) for local package installs via pipx install.

1 detail in Everything

docs update Oct 15, 2026 · issue 109

python-pipx: Adds pipx list --outdated with JSON output to show which installed packages have newer versions available.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Check which globally installed pipx tools have newer versions available, in machine-readable JSON for CI or dashboards.

$ pipx list --outdated --output json

Enforce a cooldown policy globally so pipx skips reinstalling packages that were installed within the last 7 days, across all commands.

$ export PIPX_COOLDOWN=7d

Force an immediate refresh of the shared pip without waiting for the 30-day automatic window.

$ pipx upgrade-shared

Adds PIPX_COOLDOWN environment variable as a default for --cooldown on install, install-all, inject, upgrade, upgrade-all, and run, so a single release-age policy covers every command; --cooldown 0 opts a single command out.
Runs reinstall-all, upgrade-all, and install-all across venvs in parallel.
Defers every import, including dependencies, on Python 3.15 for faster startup; set PYTHON_LAZY_IMPORTS=normal to opt out, with entry point pipx.__main__.
Retries uv-backend installs on a Python matching requires-python, as pip does.
Places --suffix last in app names, except before a Windows file extension.

Adds PIPX_COOLDOWN environment variable as a default for --cooldown on install, install-all, inject, upgrade, upgrade-all, and run, so a single release-age policy covers every command; --cooldown 0 opts a single command out.

4 more in Everything

docs update Oct 15, 2026 · issue 109

pipx now documents pipx.run entry point group, shell completion auto-linking via PIPX_COMPLETION_DIR, and pipx_metadata.json detection for package authors.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ USE IT

Declare a pipx.run entry point so pipx run my-package works even when the console script name differs from the package name.

pyproject.toml

[project.entry-points."pipx.run"]
my-package = "my_package.cli:main"

Ship bash, zsh, and fish completions inside a wheel so pipx links them automatically on install and removes them on uninstall.

setup.py

setup(
    name="your-tool",
    data_files=[
        ("share/bash-completion/completions", ["completions/your-tool"]),
        ("share/zsh/site-functions", ["completions/_your-tool"]),
        ("share/fish/vendor_completions.d", ["completions/your-tool.fish"]),
    ],
)

Detect a pipx-managed installation at runtime to surface a pipx inject recovery hint instead of generic installer advice.

python

import json, sys
from pathlib import Path

def pipx_environment() -> str | None:
    try:
        metadata = json.loads((Path(sys.prefix) / "pipx_metadata.json").read_text(encoding="utf-8"))
    except (json.JSONDecodeError, OSError):
        return None
    environment = metadata.get("environment") if isinstance(metadata, dict) else None
    return environment if isinstance(environment, str) else None

env = pipx_environment()
if env:
    print(f"Run: pipx inject {env} 'mytool[feature]'")

Adds support for a pipx.run entry point group in pyproject.toml (under [project.entry-points.'pipx.run']) and setup.cfg (under [options.entry_points] pipx.run) so package authors can declare which function pipx run PACKAGE invokes, taking priority over console scripts.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Exposes gui-scripts entry points declared in [project.gui-scripts] (pyproject.toml), gui_scripts (setup.cfg), or entry_points (setup.py) so GUI apps on Windows launch without a console window.
Auto-links shell completion scripts shipped in share/bash-completion/completions/, share/fish/vendor_completions.d/, and share/zsh/site-functions/ wheel directories under PIPX_COMPLETION_DIR (default ~/.local/share), so completions arrive and leave with the package.
Records the installed environment name in pipx_metadata.json (at sys.prefix/pipx_metadata.json) so package code can read the environment field to give pipx-specific recovery instructions such as pipx inject ENVIRONMENT 'mytool[feature]'.
Supports shipping man pages as data files via [tool.setuptools.data-files] (share/man/man1) or [tool.pdm.build.wheel-data] so pipx exposes them the same way it exposes apps.

5 details in Everything

docs update Oct 15, 2026 · issue 109

pipx adds --output json machine-readable envelope output to most commands, enabling scripted pipx workflows.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Parse pipx install results in a script — capture only the JSON envelope on stdout while progress noise goes to stderr.

$ pipx install cowsay --output json | python3 -c "import sys,json; r=json.load(sys.stdin); print(r['status'], r['exit_code'])"

Export the full installed-package snapshot and replay it on another machine using install-all.

$ pipx list --output json > pipx.json && pipx install-all pipx.json

Check every installed tool for updates in CI and surface failures via the structured errors array.

$ pipx upgrade-all --output json | python3 -c "import sys,json; r=json.load(sys.stdin); [print(e['code'], e['message']) for e in r['errors']]"

Adds --output json flag to most pipx commands (install, inject, uninject, expose, unexpose, pin, unpin, upgrade, upgrade-all, upgrade-shared, uninstall, uninstall-all, reinstall, reinstall-all, reset, health, repair, manifest lock, manifest sync, interpreter list, interpreter prune, interpreter upgrade, cache dir, cache purge, and list --outdated) to emit a structured JSON envelope on stdout instead of human-readable text.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Defines a versioned JSON envelope schema with top-level keys pipx_result_version (currently "1"), command, status ("success", "partial", or "error"), exit_code, data, and errors (each error carrying code, message, and optional environment and package fields).
Errors that occur after argument parsing — including an invalid PIPX_COOLDOWN environment variable, an unresolvable --python, a path or URL where a package name is expected, or --backend uv without a uv executable — are surfaced inside the envelope with status: "error" and code: pipx_error rather than plain text.
Adds pipx list --output json (without --outdated) to emit the installed-package snapshot format (schema key pipx_spec_version, currently "0.1", plus a venvs map) that install-all can consume directly.
Retains pipx list --json as a legacy alias for the list snapshot output; all other commands must use --output json.

5 details in Everything

docs update Oct 15, 2026 · issue 109

pipx documents all environment variables, including new PIPX_COOLDOWN, PIPX_FETCH_PYTHON, PIPX_DEFAULT_BACKEND, and PIPX_DISABLE_SHARED_LIBS_AUTO_UPGRADE settings.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Pin all new installs to use pip as the backend, overriding the uv default, so CI environments behave consistently regardless of whether uv is present.

$ export PIPX_DEFAULT_BACKEND=pip
pipx install ansible

Avoid installing packages whose index artifacts were uploaded less than 7 days ago, reducing exposure to typosquatting or accidental publishes.

$ export PIPX_COOLDOWN=7
pipx install httpie

Inspect every resolved path and backend that the current pipx installation will use, without making any changes.

$ pipx environment

Sets PIPX_DEFAULT_BACKEND to pip or uv to choose the backend for new virtual environments; defaults to uv when uv 0.9.17 or newer is available, else pip.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Sets PIPX_COOLDOWN to ignore index artifacts uploaded fewer than N days ago across install, install-all, inject, upgrade, upgrade-all, and run; overridden per-command by --cooldown.
Sets PIPX_FETCH_PYTHON to always, missing, or never to control when pipx fetches a standalone Python build (default: never), and supports PIPX_FETCH_MISSING_PYTHON as a deprecated alias for PIPX_FETCH_PYTHON=missing.
Sets PIPX_DISABLE_SHARED_LIBS_AUTO_UPGRADE to a truthy value to skip automatic shared library upgrades.
Sets PIPX_USE_EMOJI to y, yes, t, true, or on (case-insensitive) to force emoji output, or any other value to disable it.

+4 more show less

Sets PIPX_DEFAULT_PYTHON to specify the Python interpreter used when --python is not passed.
Sets PIPX_HOME, PIPX_BIN_DIR, PIPX_MAN_DIR, PIPX_COMPLETION_DIR, and PIPX_SHARED_LIBS to override per-user install paths, and PIPX_GLOBAL_HOME, PIPX_GLOBAL_BIN_DIR, PIPX_GLOBAL_MAN_DIR, and PIPX_GLOBAL_COMPLETION_DIR to override global install paths used with --global.
Sets PIPX_MAX_LOGS to control how many command logs are retained in the log directory.
Forwards standard PIP_* environment variables to pip, while forcing PIP_USER=0 and PIP_DISABLE_PIP_VERSION_CHECK=1, dropping PIP_TARGET, and defaulting PIP_KEYRING_PROVIDER to subprocess.

Sets PIPX_DEFAULT_BACKEND to pip or uv to choose the backend for new virtual environments; defaults to uv when uv 0.9.17 or newer is available, else pip.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Sets PIPX_COOLDOWN to ignore index artifacts uploaded fewer than N days ago across install, install-all, inject, upgrade, upgrade-all, and run; overridden per-command by --cooldown.
Sets PIPX_FETCH_PYTHON to always, missing, or never to control when pipx fetches a standalone Python build (default: never), and supports PIPX_FETCH_MISSING_PYTHON as a deprecated alias for PIPX_FETCH_PYTHON=missing.
Sets PIPX_DISABLE_SHARED_LIBS_AUTO_UPGRADE to a truthy value to skip automatic shared library upgrades.
Sets PIPX_USE_EMOJI to y, yes, t, true, or on (case-insensitive) to force emoji output, or any other value to disable it.

+1 more show less

Sets PIPX_MAX_LOGS to control how many command logs are retained in the log directory.

3 more in Everything

docs update Oct 15, 2026 · issue 109

pipx gains install-all, uninject, expose/unexpose, pin/unpin, manifest, interpreter, cache, health, repair, exec commands plus json output and uv backend support⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Export installed package list as JSON, then restore all environments on a new machine using the new install-all subcommand.

$ pipx list --output json > pipx-spec.json
pipx install-all pipx-spec.json --backend uv

Install a tool pinned to a specific Python version fetched automatically, with a supply-chain cooldown to avoid freshly-uploaded artifacts.

$ pipx install black --python 3.12 --fetch-python missing --cooldown 3 --backend uv

Set org-wide defaults so all pipx invocations use uv, enforce a 7-day artifact cooldown, and store global installs in a custom path.

$ export PIPX_DEFAULT_BACKEND=uv
export PIPX_COOLDOWN=7
export PIPX_GLOBAL_HOME=/opt/pipx

Adds --upgrade flag (-U) to pipx install to upgrade or downgrade an existing package when its version does not satisfy the supplied spec.
Adds new subcommands pipx install-all (installs all packages from a spec metadata file generated via pipx list --output json, installing up to eight environments in parallel), pipx uninject (uninstalls injected packages from an existing pipx-managed virtual environment), pipx expose and pipx unexpose, pipx pin and pipx unpin, pipx manifest, pipx interpreter, pipx cache, pipx health, pipx repair, and pipx exec.
Adds PIPX_GLOBAL_HOME, PIPX_GLOBAL_BIN_DIR, PIPX_GLOBAL_MAN_DIR, and PIPX_GLOBAL_COMPLETION_DIR environment variables for overriding global-mode paths when --global is used, along with PIPX_COMPLETION_DIR for overriding shell completion installation locations and PIPX_MAN_DIR for overriding the manual pages installation location.
Adds PIPX_USE_EMOJI environment variable to override emoji behavior.

Adds new subcommands pipx install-all (installs all packages from a spec metadata file generated via pipx list --output json, installing up to eight environments in parallel), pipx uninject (uninstalls injected packages from an existing pipx-managed virtual environment), pipx expose and pipx unexpose, pipx pin and pipx unpin, pipx manifest, pipx interpreter, pipx cache, pipx health, pipx repair, and pipx exec.
Adds PIPX_GLOBAL_HOME, PIPX_GLOBAL_BIN_DIR, PIPX_GLOBAL_MAN_DIR, and PIPX_GLOBAL_COMPLETION_DIR environment variables for overriding global-mode paths when --global is used, along with PIPX_COMPLETION_DIR for overriding shell completion installation locations and PIPX_MAN_DIR for overriding the manual pages installation location.
Adds PIPX_USE_EMOJI environment variable to override emoji behavior.

1 more in Everything

docs update Oct 15, 2026 · issue 109

pipx gains health, repair, and reset commands plus --fetch-python, PIPX_MAX_LOGS, and lazy-import controls for Python 3.15⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Check all managed environments for interpreter health in CI before running tools, getting machine-readable output for automated triage.

$ pipx health --output json

Rebuild only the broken environments that reference a specific interpreter version after a Python upgrade.

$ pipx repair --python python3.13

Install a tool using a freshly downloaded standalone Python 3.12 build to avoid a patched or EOL distro interpreter.

$ pipx install my-package --python python3.12 --fetch-python=missing

Adds pipx health command to check every managed environment's Python interpreter without modifying it; exits with status 1 on failure, accepts package names to check a subset, and supports --output json for scripting (unhealthy environments appear in errors with code environment_unhealthy).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds pipx repair command to rebuild broken environments using recorded metadata, with --python to target a specific interpreter; skips healthy environments and refuses pinned packages (run pipx unpin PACKAGE first).
Adds pipx reset command to wipe all managed packages, shared libraries, caches, standalone interpreters, logs, and trash back to install-time state; supports --yes for scripted use and --dry-run to preview removals.
Adds PIPX_MAX_LOGS environment variable to control how many command logs and error logs pipx retains (default: last 10 of each).
Documents pipx environment --value PIPX_LOG_DIR to locate verbose per-command logs, including cmd_<timestamp>_pip_errors.log and cmd_<timestamp>_uv_errors.log written alongside failed runs.

+4 more show less

Documents pipx environment --value PIPX_UV_BINARY to find the uv binary pipx uses, enabling direct uv cache dir / uv cache clean calls for cache management under the uv backend.
Documents pipx environment --value PIPX_VENV_CACHEDIR to locate the venv cache directory.
Documents pipx environment --value PIPX_DEFAULT_PYTHON to inspect which Python interpreter pipx uses by default.
Documents --pip-args= (with = sign) syntax for passing pip arguments such as --no-cache-dir or --trusted-host to pipx install.

Adds pipx health command to check every managed environment's Python interpreter without modifying it; exits with status 1 on failure, accepts package names to check a subset, and supports --output json for scripting (unhealthy environments appear in errors with code environment_unhealthy).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds pipx repair command to rebuild broken environments using recorded metadata, with --python to target a specific interpreter; skips healthy environments and refuses pinned packages (run pipx unpin PACKAGE first).
Adds pipx reset command to wipe all managed packages, shared libraries, caches, standalone interpreters, logs, and trash back to install-time state; supports --yes for scripted use and --dry-run to preview removals.
Adds PIPX_MAX_LOGS environment variable to control how many command logs and error logs pipx retains (default: last 10 of each).

5 more in Everything

└──▷ BREAKING ON UPGRADE

!Apps installed with --suffix on pipx 1.17.14 or earlier used the old naming scheme (e.g. pip3_old.12); after upgrading, the next pipx upgrade, reinstall, inject, or expose of the environment renames the app to the new scheme (e.g. pip3.12_old) — scripts and aliases referencing the old name will break.

docs update Oct 15, 2026 · issue 109

pipx gains a uv backend: install with [uv] extra or set PIPX_DEFAULT_BACKEND=uv to replace pip/venv with uv across all commands.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Enable the uv backend globally so all new venvs use uv without passing a flag every time.

$ PIPX_DEFAULT_BACKEND=uv pipx install ruff

Override the default backend for a single install — useful when a package requires pip-specific flags uv does not support.

$ pipx install black --backend pip

Verify that new venvs will use the uv backend after installing pipx with the bundled uv extra.

$ pipx install pipx[uv] && pipx environment --value PIPX_RESOLVED_BACKEND

Adds the --backend flag (accepted by install, install-all, inject, upgrade, upgrade-all, reinstall, reinstall-all, and run) to choose uv or pip per invocation; the PIPX_DEFAULT_BACKEND environment variable to set the backend globally, with pipx auto-selecting uv when uv 0.9.17+ is bundled or found on PATH; PIPX_RESOLVED_BACKEND, inspectable via pipx environment --value PIPX_RESOLVED_BACKEND, to confirm which backend pipx will use for new venvs; and the ability to switch an already-installed app's backend with pipx reinstall NAME --backend uv.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds PIPX_COOLDOWN environment variable (and --cooldown DAYS flag) that maps to uv's --exclude-newer P{DAYS}D when the uv backend is active.
Supports pipx install pipx[uv] extra to ship a bundled uv binary alongside pipx.
Switches pipx runpip to run uv pip <args> --python <venv>/bin/python and pipx run to exec uv tool run under the uv backend, with cache living in UV_CACHE_DIR instead of PIPX_VENV_CACHEDIR.
Supports pipx run script.py via uv run --script script.py for PEP 723 inline scripts under the uv backend.

Adds the --backend flag (accepted by install, install-all, inject, upgrade, upgrade-all, reinstall, reinstall-all, and run) to choose uv or pip per invocation; the PIPX_DEFAULT_BACKEND environment variable to set the backend globally, with pipx auto-selecting uv when uv 0.9.17+ is bundled or found on PATH; PIPX_RESOLVED_BACKEND, inspectable via pipx environment --value PIPX_RESOLVED_BACKEND, to confirm which backend pipx will use for new venvs; and the ability to switch an already-installed app's backend with pipx reinstall NAME --backend uv.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds PIPX_COOLDOWN environment variable (and --cooldown DAYS flag) that maps to uv's --exclude-newer P{DAYS}D when the uv backend is active.
Supports pipx install pipx[uv] extra to ship a bundled uv binary alongside pipx.
Supports pipx run script.py via uv run --script script.py for PEP 723 inline scripts under the uv backend.

1 more in Everything

└──▷ BREAKING ON UPGRADE

!Under the uv backend, pipx run caches in UV_CACHE_DIR instead of PIPX_VENV_CACHEDIR; old pipx-managed run caches are not migrated and must be removed manually with pipx cache purge.
!pipx install pip --backend uv errors because uv venvs contain no pip; use --backend pip to install pip itself.
!pipx run --backend uv rejects --system-site-packages; use --backend pip when you need system site packages.
!Some --pip-args values (e.g. --editable, --no-build-isolation) have no uv tool run equivalent; pipx errors rather than silently dropping them under the uv backend.

docs update Oct 15, 2026 · issue 109

pipx now upgrades and rebuilds up to eight environments in parallel, with safe interrupt handling and ordered output.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Upgrade all installed apps in parallel (up to 8 at once); use --verbose to fall back to sequential output for debugging credential prompts.

$ pipx upgrade-all --verbose

Upgrades up to eight environments at once via pipx upgrade-all, printing output in environment order; a failed environment does not block the others.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Pass --verbose to pipx upgrade-all to force one-at-a-time execution and see pip/uv output in real time.
Ctrl-C, SIGTERM, or SIGHUP during a parallel upgrade stops new upgrades from starting, lets in-progress ones finish, flags any environment cut short, and triggers automatic reinstall on the next upgrade or install of that environment.
Rebuilds up to eight environments in parallel (capped by CPU count), holding each environment's output until prior ones finish so the log reads identically to a sequential run.

Upgrades up to eight environments at once via pipx upgrade-all, printing output in environment order; a failed environment does not block the others.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

3 more in Everything

1.18.0 Oct 15, 2026 · issue 109

pipx 1.18.0 adds parallel multi-env operations, graceful Ctrl-C handling, and Python 3.15 lazy-import startup.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION

$ git clone --branch 1.18.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.18.0

└──▷ TRY IT

Upgrade all installed environments in parallel on Python 3.15 for maximum speed, then fall back to sequential output if you need to read per-env logs.

$ pipx upgrade-all --verbose

Install all recorded environments using uv as the backend, automatically translating any pip index options stored in the spec file.

$ pipx install-all --backend uv

Opt out of Python 3.15 lazy imports if a tool misbehaves at startup due to deferred module loading.

$ PYTHON_LAZY_IMPORTS=normal pipx run mytool

Sets PYTHON_LAZY_IMPORTS=normal to disable lazy imports that Python 3.15 uses to accelerate pipx startup.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Adds --backend flag to install-all to translate recorded index options between pip and uv backends, refusing environments whose index cannot be carried over.
reinstall-all, upgrade-all, and install-all now operate on several environments in parallel; pass --verbose to force sequential execution.
Runs pipx upgrade-shared to refresh shared pip on demand rather than waiting for the 30-day automatic refresh window.

Sets PYTHON_LAZY_IMPORTS=normal to disable lazy imports that Python 3.15 uses to accelerate pipx startup.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

3 more in Everything

└──▷ BREAKING ON UPGRADE

!--suffix now appends after the app name (e.g. pip3.12@1 instead of pip3@1.12), except before a Windows file extension; apps exposed by 1.17.14 keep their old name until pipx next exposes them.
!PIPX_MAX_LOGS now keeps exactly that many logs, not one extra — environments relying on the previous off-by-one count will see one fewer log file retained.

docs update Oct 3, 2026 · issue 093

pipx now installs local PEP 723 scripts by filename, derives command names from filenames, and recovers gracefully from missing metadata on uninstall.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT

Install a local PEP 723 script whose filename looks like a PyPI package name, so pipx treats it as a file rather than a registry lookup.

$ pipx install bare.py

Adds pipx install bare.py support: installs a local PEP 723 script from its file when the path reads as a PyPI name, contains [, or starts with a quoted ~, and suppresses misleading PyPI upgrade hints for scripts.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Derives local script command names from the script's filename when parent directories contain #, replacing the previous behaviour of using the directory name.
Allows pipx uninstall and pipx uninstall-all to remove an environment with no pipx metadata or a dead interpreter instead of crashing.

Adds pipx install bare.py support: installs a local PEP 723 script from its file when the path reads as a PyPI name, contains [, or starts with a quoted ~, and suppresses misleading PyPI upgrade hints for scripts.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

2 more in Everything

└──▷ BREAKING ON UPGRADE

!Local scripts previously installed under their parent directory's name (when the directory contained #) are no longer upgradeable in place — uninstall and reinstall them to get the corrected filename-derived command name.

docs update Oct 3, 2026 · issue 093

pipx gains --app flag to override the command name when running a local script⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

docs update Aug 31, 2026 · issue 060

pipx 1.17.0 adds PIPX_COOLDOWN env var as a global default for --cooldown across all commands.

└──▷ TRY IT

Set a global cooldown policy so every pipx install or upgrade skips packages released less than 3 days ago, without passing --cooldown to each command.

$ export PIPX_COOLDOWN=3
pipx install <package>

Override the global cooldown for a single command — useful when you explicitly want to install a just-released package.

$ PIPX_COOLDOWN=3 pipx install --cooldown 0 <package>

Adds PIPX_COOLDOWN environment variable to set a global default for --cooldown, so a single release-age policy applies to every pipx command; an explicit --cooldown flag still takes precedence, --cooldown 0 opts a single command out, and locked installs ignore the variable rather than failing.
Extends pipx run --spec <spec> <app> on the uv backend to build a pipx-managed venv when the app name differs from the spec's normalized distribution name, or when the spec carries no name at all, so pipx correctly honors the package's [pipx.run] entry point.
Adds PIPX_MAX_LOGS as a valid value for pipx environment --value, so it can now be queried without exiting with invalid choice.

3 details in Everything

└──▷ BREAKING ON UPGRADE

!Requires packaging>=26; earlier releases serialize a direct reference as name@ url rather than PEP 508's name @ url, so upgrading changes how specifiers are recorded and passed to the backend.

docs update Aug 31, 2026 · issue 060

└──▷ TRY IT

Install a tool while skipping packages published to PyPI in the last 7 days, guarding against a dependency confusion or typosquatting window.

$ pipx install --cooldown 7 httpie

Set a persistent cooldown default so every pipx install/upgrade/run skips artifacts newer than 3 days without passing the flag each time.

$ export PIPX_COOLDOWN=3

Adds --global option support that overrides default pipx home, app, and manual pages locations system-wide.
Adds {human,json} output format selection across multiple commands.
Adds {pip,uv} backend selection across multiple commands.

docs update Aug 30, 2026 · issue 059

pipx 1.17.0 adds PIPX_COOLDOWN env var for release-age policy and requires packaging>=26

└──▷ TRY IT

Set a project-wide release-age cooldown so every pipx command respects the policy without repeating --cooldown on each invocation.

$ export PIPX_COOLDOWN=86400
pipx install httpie

Adds PIPX_COOLDOWN environment variable to set a default for --cooldown, so a single release-age policy applies to every command without repeating the flag; an explicit --cooldown still takes precedence, --cooldown 0 opts a single command out, and locked installs ignore the variable rather than failing.
Requires packaging>=26, which correctly serializes direct references as name @ url (PEP 508) instead of name@ url, ensuring the specifier pipx records and passes to the backend is consistent regardless of which version happened to be installed previously.

2 details in Everything

└──▷ BREAKING ON UPGRADE

!Now requires packaging>=26; environments pinned to an earlier packaging release will need to upgrade before pipx 1.17.0 will work.

docs update Aug 30, 2026 · issue 059

pipx adds PIPX_COOLDOWN env var to skip recently uploaded index artifacts across install and upgrade commands

└──▷ TRY IT

Set a global cooldown so pipx never auto-installs or upgrades to packages published within the last 3 days, reducing exposure to supply-chain attacks on freshly pushed releases.

$ export PIPX_COOLDOWN=3
pipx upgrade-all

docs update Aug 30, 2026 · issue 059

pipx adds --cooldown flag and PIPX_COOLDOWN env var to ignore recently uploaded index artifacts

└──▷ TRY IT

Install a tool while ignoring packages published in the last 3 days, guarding against dependency confusion or typosquatting attacks on freshly uploaded releases.

$ pipx install --cooldown 3 <package>

Set a default cooldown for all pipx commands in your shell profile so every install and upgrade skips artifacts newer than 7 days without passing the flag each time.

$ export PIPX_COOLDOWN=7

Adds --cooldown DAYS flag (accepted by install, upgrade, run, and other commands) to ignore index artifacts uploaded fewer than DAYS days ago, reducing risk from freshly published or potentially malicious packages.
Adds PIPX_COOLDOWN environment variable to set the default --cooldown value globally; pass 0 to opt out.
Adds PIPX_DEFAULT_BACKEND environment variable, joining PIPX_FETCH_MISSING_PYTHON, PIPX_FETCH_PYTHON, PIPX_DISABLE_SHARED_LIBS_AUTO_UPGRADE, and PIPX_USE_EMOJI as newly documented env vars.
Adds --global option to pipx install, redirecting home, app, and manual pages locations to system-wide paths.

4 details in Everything

docs update Aug 30, 2026 · issue 059

└──▷ TRY IT

Install a tool while skipping any release uploaded in the last 7 days, giving the community time to catch and yank bad releases.

$ pipx install --cooldown 7 httpie

Apply a machine-wide 7-day cooldown to every pipx install and upgrade without repeating the flag — add to your shell profile to persist across sessions.

$ export PIPX_COOLDOWN=7
pipx upgrade-all

Verify the cooldown value pipx recorded for an installed environment after install or upgrade.

$ pipx list --output json | jq '.venvs.httpie.metadata.main_package.cooldown_days'

Adds --cooldown DAYS flag to install, install-all, inject, upgrade, upgrade-all, and run commands to skip index artifacts uploaded within the specified number of days, reducing exposure to compromised or broken releases before they can be yanked.
Adds PIPX_COOLDOWN environment variable to apply a machine-wide cooldown policy to all supported commands without passing a flag each time.
Translates the cooldown policy to both pip (--uploaded-prior-to P7D) and uv (--exclude-newer P7D) backends automatically; uv backend requires version 0.9.17 or newer for relative cooldowns.
Records cooldown_days in each environment's metadata, so the last-used cooldown value persists and can be inspected via pipx list --output json.
Passing --cooldown 0 opts a single command out of a machine-wide PIPX_COOLDOWN setting.

+1 more show less

Passing --cooldown together with --lock is an error; a pylock.toml-locked install ignores PIPX_COOLDOWN silently and proceeds.

docs update Aug 30, 2026 · issue 059

pipx gains a --cooldown flag and PIPX_COOLDOWN env var to delay installs/upgrades until a release is N days old

└──▷ TRY IT

Install a tool only if its release is at least 7 days old, so you avoid the highest-risk window after a new publish.

$ pipx install --cooldown 7 black

Set a global 7-day cooldown for every tool so all future installs and upgrades wait out the highest-risk post-release window.

$ export PIPX_COOLDOWN=7

Adds --cooldown <days> flag to pipx install to skip releases newer than the specified number of days, reducing exposure to broken or compromised fresh releases; the lag is persisted per-package so subsequent pipx upgrade calls honour it without repeating the flag.
Adds PIPX_COOLDOWN environment variable to apply a global release-age lag to every tool install and upgrade without passing --cooldown each time.

2 details in Everything

1.17.0 Aug 29, 2026 · release notes

Adds PIP_COOLDOWN environment variable and --cooldown flag for age-based policy on install, upgrade and run commands

Add PIPX_COOLDOWN, a default for –cooldown on install , install-all , inject , upgrade , upgrade-all and run , so one release-age policy covers every command. An explicit –cooldown still wins, –cooldown 0 opts a single command out, and a locked install ignores the variable rather than failing.
Require packaging>=26 . Earlier releases serialize a direct reference as name@ url rather than PEP 508’s name @ url , so the specifier pipx recorded in pipx_metadata.json and passed to the backend depended on which packaging happened to be installed.

2 details in Everything

docs update Jul 30, 2026 · issue 030

pipx 1.16.5 honors version specifiers in upgrade --install; 1.16.4 ships colorama in zipapp and adds log pruning via PIPX_MAX_LOGS=0

└──▷ TRY IT

Upgrade a package (or install it if missing) while enforcing a version pin — now respects the specifier correctly.

$ pipx upgrade --install 'cowsay<6'

Keep the pipx log directory clean by pruning all log files on each run.

$ PIPX_MAX_LOGS=0 pipx install httpie

Respects version specifiers when pipx upgrade --install installs a missing package, so pinned versions are enforced correctly.
Bundles colorama in the zipapp, enabling the single-file pipx to work on Windows and Python 3.10 without extra dependencies.
Setting PIPX_MAX_LOGS=0 now prunes all pipx log files instead of retaining them indefinitely.

3 details in Everything

1.16.4 Jul 29, 2026 · release notes

pipx 1.16.4 enables PIPX_MAX_LOGS=0 to prune logs; bundles colorama/tomli in zipapp for Windows/3.10 compatibility.

1.15.1 Jul 15, 2026 · issue 017

pipx 1.15.1 adds outdated, exec, reset, PEP 751 lock file support, scriptable JSON output, and major performance improvements.

└──▷ GET THIS VERSION

$ git clone --branch 1.15.1 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.15.1

└──▷ TRY IT

Check which of your globally installed tools have newer versions available before deciding what to upgrade.

$ pipx outdated

Filter pipx list output to inspect a single installed package without scrolling through everything.

$ pipx list black

Start fresh after a corrupted pipx state — wipes all managed environments and reinitialises pipx.

$ pipx reset

New pipx outdated command lists all installed tools that have upgrades available.
New pipx exec command runs an already-installed application directly without re-resolving environments.
New pipx reset command wipes and rebuilds pipx's state from a clean install.
New pipx cache subcommand manages cached pipx run environments.
Adds PEP 751 lock file support for pipx install, enabling reproducible installs from lock files.

+17 more show less

Adds scriptable/machine-readable output format selection across install, inject, pin, uninstall, and other commands.
Adds --skip-maintenance flag (feat: allow skipping maintenance) to bypass shared-library upkeep during operations.
New pipx health repair mode automatically fixes broken virtual environments.
Enables pipx expose to selectively link dependency apps and completion scripts a package ships.
Supports pipx inject with main-package extras, allowing extras on the primary package to be activated at inject time.
Adds pipx install guidance for library-only packages that ship no CLI entrypoints.
Adds Python interpreter argument passthrough for pipx run.
Adds pipx list filtering by package name to show details for a single installed tool.
Adds pipx install support for persisting PEP 723 inline-scripted Python scripts as permanent tools.
Adds download progress bar when pipx install fetches packages.
Streams verbose installer output live during pipx install --verbose.
Installs a pipx man page from wheels.
Parallelizes update checks in pipx upgrade-all for significantly faster operation.
Multiple startup-path performance improvements (lazy venv scans, cached site-packages paths, deferred Python resolution) that speed up every pipx invocation.
Adds pipx manifest sync to reconcile a set of managed tools from a declarative manifest.
Adds dependency cooldown policy controls to prevent overly frequent automatic dependency updates.
Adds upgrade result reporting to pipx upgrade output, showing what changed.

22 details in Everything

1.16.0 Jul 15, 2026 · release notes

pipx 1.16 adds structured JSON output via --output, pipx reset, PEP 751 support, and new diagnostic commands.

└──▷ TRY IT

Get a scriptable JSON list of outdated packages

$ pipx list --outdated --output json

Completely reset pipx state for a fresh install

$ pipx reset --yes

Adds --output json flag to structured commands (e.g., pipx list, pipx upgrade) for scriptable results
Adds pip_result_version 1 envelope containing command tokens, status, exit code, data, and errors for new JSON output
Adds pipx reset subcommand to uninstall all packages and remove caches with --yes or --dry-run options
Adds support for installing PEP 751 lock files directly
Adds pipx exec ENVIRONMENT APPLICATION subcommand to run applications within installed environments

+2 more show less

Adds pipx cache and pipx run --refresh subcommands
Adds --fetch-python=missing flag to allow downloading Python interpreters when not present on the system

7 details in Everything

└──▷ BREAKING ON UPGRADE

!The --json alias was removed for all commands except pipx list in favour of --output json
!Top-level pipx lock and pipx sync commands are moved under pipx manifest, requiring usage of pipx manifest lock and pipx manifest sync instead

1.15.0 Jun 24, 2026 · release notes

pipx 1.15.0 adds --dry-run to ensurepath so you can preview PATH changes before applying them.

└──▷ GET THIS VERSION

$ git clone --branch 1.15.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.15.0

└──▷ TRY IT

Preview what ensurepath would add to your PATH before committing to the change.

$ pipx ensurepath --dry-run

1.15.0 Jun 24, 2026 · issue 001

pipx 1.15.0 adds --dry-run to ensurepath so you can preview PATH changes before applying them.

└──▷ GET THIS VERSION

$ git clone --branch 1.15.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.15.0

└──▷ TRY IT

Check what PATH changes pipx would make on a new machine before committing to them — useful in provisioning scripts or CI setup validation.

$ pipx ensurepath --dry-run

1.14.0 Jun 4, 2026 · release notes

pipx 1.14.0 adds --no-path-check to skip PATH validation in pipx run

└──▷ GET THIS VERSION

$ git clone --branch 1.14.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.14.0

└──▷ TRY IT

Run a tool in a CI or container environment where pipx's bin dir is not on PATH and you want to suppress the PATH warning.

$ pipx run --no-path-check black .

1.14.0 Jun 4, 2026 · issue 001

pipx 1.14.0 adds --no-path-check to skip the on-PATH check in pipx run

└──▷ GET THIS VERSION

$ git clone --branch 1.14.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.14.0

└──▷ TRY IT

Run a tool in a temporary environment without triggering PATH-check warnings — handy in CI pipelines or containers where pipx's bin dir is intentionally absent from PATH.

$ pipx run --no-path-check black --check .

1.13.0 May 30, 2026 · release notes

pipx 1.13.0 adds opt-out for automatic shared library upgrades and refreshes the legacy standalone Python index cache.

└──▷ GET THIS VERSION

$ git clone --branch 1.13.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.13.0

Adds opt-out flag for shared libs auto-upgrade, letting users suppress automatic shared library upgrades on install/inject.
Refreshes the legacy standalone Python index cache, keeping Python version resolution current without manual intervention.

2 details in Everything

1.12.0 May 6, 2026 · release notes

pipx 1.12.0 adds an opt-in uv backend and always-fetch mode for standalone Python interpreters.

└──▷ GET THIS VERSION

$ git clone --branch 1.12.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.12.0

Adds opt-in uv backend for faster package installation and environment management.
Supports always fetching a standalone Python interpreter, ensuring a consistent runtime regardless of system Python.

2 details in Everything

1.11.2 May 5, 2026 · release notes

pipx 1.11.2 adds a help subcommand alias and drops Python 3.9 support.

└──▷ GET THIS VERSION

$ git clone --branch 1.11.2 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.11.2

└──▷ TRY IT

Use the new help subcommand as an alternative to --help for quick reference at the terminal.

$ pipx help

Adds help as a subcommand alias, giving users an alternative way to invoke top-level help.

1 detail in Everything

└──▷ BREAKING ON UPGRADE

!Python 3.9 is no longer supported; pipx 1.11.2 requires Python 3.10 or later.

1.11.0 Mar 23, 2026 · release notes

pipx 1.11.0 adds PIPX_MAX_LOGS env var to control how many log files are retained.

└──▷ GET THIS VERSION

$ git clone --branch 1.11.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.11.0

└──▷ TRY IT

Limit pipx log retention to the last 5 runs to keep your log directory tidy.

$ PIPX_MAX_LOGS=5 pipx install <package>

New PIPX_MAX_LOGS environment variable controls the maximum number of pipx log files retained.

1 detail in Everything

1.10.0 Mar 18, 2026 · release notes

pipx 1.10.0 adds --with option to pipx run for injecting extra packages into ephemeral environments.

└──▷ GET THIS VERSION

$ git clone --branch 1.10.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.10.0

└──▷ TRY IT

Run a tool with an additional dependency available in the same ephemeral environment — useful when a CLI plugin or extra isn't bundled by default.

$ pipx run <package> --with <extra-package>

1.9.0 Mar 17, 2026 · release notes

pipx 1.9.0 adds environment variable tab-completion and raises on reinstall of pinned packages.

└──▷ GET THIS VERSION

$ git clone --branch 1.9.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.9.0

Adds tab-completion support for environment variables in pipx commands.

1 detail in Everything

└──▷ BREAKING ON UPGRADE

!pipx reinstall now raises an exception if the target package is pinned, rather than silently proceeding.

1.8.0 Sep 30, 2025 · release notes

pipx 1.8.0 adds --all-shells flag to ensure_path, Python 3.13 support, and renames the USE_EMOJI env var.

└──▷ GET THIS VERSION

$ git clone --branch 1.8.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.8.0

└──▷ TRY IT

After installing pipx on a new machine with multiple shells (bash, zsh, fish), update all shell profiles in one shot instead of running ensurepath per shell.

$ pipx ensurepath --all-shells

Adds --all-shells flag to pipx ensurepath to inject the pipx bin path into every detected shell profile at once.
Supports Python 3.13 as a runtime environment for installed tools.
Renames the USE_EMOJI environment variable to PIPX_USE_EMOJI for consistent namespacing.

3 details in Everything

└──▷ BREAKING ON UPGRADE

!The USE_EMOJI environment variable is renamed to PIPX_USE_EMOJI; any script or config that sets USE_EMOJI to control emoji output will have no effect after upgrading.
!Python 3.8 is no longer supported; pipx will not run on Python 3.8 interpreters after upgrading.

1.7.0 Aug 22, 2024 · release notes

pipx 1.7.0 adds --prepend to ensurepath, a new env var for spaces in home paths, and multi-suffix standalone Python support.

└──▷ GET THIS VERSION

$ git clone --branch 1.7.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.7.0

└──▷ TRY IT

Ensure pipx's bin dir takes priority over system tools by prepending it to PATH rather than appending.

$ pipx ensurepath --prepend

Adds --prepend option to pipx ensurepath to insert pipx's bin directory at the front of PATH instead of appending it.
Introduces a new environment variable to allow spaces in the pipx home path.
Supports multiple machine suffixes when resolving standalone Python installations.

3 details in Everything

1.6.0 Jun 2, 2024 · release notes

pipx 1.6.0 adds install-all, upgrade-shared, pin/unpin commands and text-file injection

└──▷ GET THIS VERSION

$ git clone --branch 1.6.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.6.0

└──▷ USE IT

Bulk-install environments from a spec file instead of running individual commands.

shell

pipx install-all requirements.txt

Lock a specific version of an installed package to prevent accidental upgrades.

shell

pipx pin requests==2.28.0

pipx install-all <spec_file> installs packages defined in a spec metadata file.
--inject <file> flag on pipx install allows injecting additional packages from a text file.
pipx upgrade-shared command upgrades shared dependencies for all environments.
pipx pin and pipx unpin commands lock or unlock package versions.

4 details in Everything

1.5.0 Mar 29, 2024 · release notes

pipx 1.5.0 adds interpreter command, --global flag, --install to upgrade, and standalone python downloads

└──▷ GET THIS VERSION

$ git clone --branch 1.5.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.5.0

└──▷ TRY IT

Query which python interpreter was used to install a specific package.

$ pipx interpreter package_name

Install a package globally for all system users.

$ pipx install --global package_name

Upgrade an existing package, or install it if it's missing.

$ pipx upgrade --install package_name

Adds interpreter subcommand for querying source interpreters from pipx metadata
Adds --global option to perform actions (e.g., install) for all users on the system
Adds --install flag to pipx upgrade to automatically install the package if not present
Automatically downloads and uses a standalone Python build when the specified --python version is missing

4 details in Everything

1.4.2 Jan 12, 2024 · release notes

python-pipx 1.4.2 adds --skip-maintenance and PEP 723 script support

Adds --skip-maintenance flag to the list command to allow skipping maintenance tasks during execution
Supports scripts using /// script header syntax without a run table, following updated PEP 723
Improves error message when provided --python version is not found

3 details in Everything

1.4.0 Dec 28, 2023 · release notes

pipx 1.4.0 adds bulk install support and consistent quiet/verbose modes to CLI commands

└──▷ GET THIS VERSION

$ git clone --branch 1.4.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.4.0

└──▷ USE IT

Install several tools in a single invocation to save time.

shell

pipx install black flake8 pylint

Adds pipx install support for installing multiple applications at once
Adds consistent quiet (-q) and verbose (-v) flags across all pipx subcommands

2 details in Everything

1.3.0 Dec 2, 2023 · release notes

pipx 1.3.0 adds PEP 723 script support in pipx run, --with-suffix for inject, and --preinstall for install

└──▷ GET THIS VERSION

$ git clone --branch 1.3.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.3.0

└──▷ USE IT

Inject a package into an existing app with a specific suffix to avoid conflicts

shell

pipx inject myapp requests --with-suffix
myapp --suffix -requests help

Pre-install build dependencies for a package that fails otherwise due to missing system libs or headers

shell

pipx install cryptography --preinstall

Support PEP 723 inline metadata in scripts run via pipx run <script>
Add --with-suffix flag to pipx inject <app> <pkg...> to isolate injected package namespace
Add --preinstall option to pipx install <package> to pre-install build requirements into the environment before running
Allow executing pip directly via pipx run pip for interactive use

4 details in Everything

└──▷ BREAKING ON UPGRADE

!Drops support for Python 3.7; pipx will fail to run on this version

1.2.0 Mar 12, 2023 · release notes

pipx 1.2.0 adds the uninject command and ships a zipapp distribution.

└──▷ GET THIS VERSION

$ git clone --branch 1.2.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.2.0

Adds the pipx uninject subcommand to remove previously injected dependencies from an environment
Ship a zipapp of pipx for single-file distribution

2 details in Everything

1.1.0 May 28, 2022 · release notes

pipx 1.1.0 adds the pipx environment command and a --short flag for the list subcommand

└──▷ GET THIS VERSION

$ git clone --branch 1.1.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 1.1.0

└──▷ TRY IT

Get a clean list of installed package names for scripting or auditing.

$ pipx list --short

Inspect the active paths and configuration values in your pipx environment.

$ pipx environment

list --short: Adds the --short option to the list subcommand to output only package names.
pipx environment: Adds a new environment command to inspect the current pipx environment configuration.

2 details in Everything

0.16.2.0 Apr 27, 2021 · release notes

Adds --json switch to pipx list for rich JSON metadata output

└──▷ GET THIS VERSION

$ git clone --branch 0.16.2.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 0.16.2.0

└──▷ TRY IT

Get machine-readable list of installed packages and their metadata

$ pipx list --json

Adds --json flag to pipx list CLI command
Sets minimum supported Python version to 3.6

2 details in Everything

└──▷ BREAKING ON UPGRADE

!Removed support for Python 3.5; pipx now requires at least Python 3.6

0.16.1.0 Feb 26, 2021 · release notes

Introduces pipx.run entry point group for app declaration

└──▷ GET THIS VERSION

$ git clone --branch 0.16.1.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 0.16.1.0

└──▷ USE IT

Declare an application for pipx run using the new entry point group in your package's setup configuration.

text

[metadata]
entry_points =
    pipx.run = my_package:my_function

Sped up pipx list.
pip errors no longer stream to the shell when pip fails during a pipx install; pip's output is now saved to a log file.

2 details in Everything

0.16.0.0 Jan 16, 2021 · release notes

pipx 0.16 introduces the reinstall subcommand, --upgrade-injected flags, and per-command logging.

└──▷ GET THIS VERSION

$ git clone --branch 0.16.0.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 0.16.0.0

└──▷ USE IT

Fix a broken installation of a single tool without affecting others.

shell

pipx reinstall black

Update an installed application along with its injected dependencies in one step.

shell

pipx upgrade --upgrade-injected myapp

Locate logs generated by the most recent command execution for troubleshooting.

shell

cat $(ls -t $PIPX_HOME/logs | head -n 1)

pipx reinstall <app> now reinstalls a single application's virtual environment.
Adds --upgrade-injected to pipx upgrade and pipx upgrade-all to update injected packages alongside main ones.
Adds per-command logging to $PIPX_HOME/logs (default ~/.local/pipx/logs) for every pipx execution.

3 details in Everything

0.15.6.0 Oct 17, 2020 · release notes

Add support for user-defined default python interpreter via PIPAX_DEFAULT_PYTHON

└──▷ TRY IT

Install packages using a specific Python version managed by pyenv.

$ PIPX_DEFAULT_PYTHON=$(pyenv prefix 3.12)/bin/python pipx install mypackage

Adds PIPX_DEFAULT_PYTHON environment variable to specify a custom Python interpreter.

1 detail in Everything

0.15.5.0 Aug 22, 2020 · release notes

pipx adds --suffix to install for multiple tool versions and enhances pipx list output with injected package details.

└──▷ GET THIS VERSION

$ git clone --branch 0.15.5.0 https://github.com/pypa/pipx.git
# already have the repo? check out this version:
$ git checkout 0.15.5.0

└──▷ USE IT

Install two different versions of a tool (e.g. ripgrep) side-by-side without overwriting the other.

shell

pipx install --suffix @243 ripgrep

List all installed apps including their injected dependencies, with versions shown for each injected package.

shell

pipx list --include-injected

install subcommand gains --suffix flag to allow installing multiple versions of the same tool
list command gains --include-injected option which now lists the version of each injected package after its name
ensurepath now ensures pip user binary path is in PATH when pipx was installed via pip install --user
pipx logs its own version in verbose mode

4 details in Everything

0.15.1.0 Jan 7, 2020 · release notes

pipx 0.15.1.0 adds auto-upgrade for shared libraries (e.g., pip) older than one month.

0.15.0.0 Jan 5, 2020 · release notes

pipx 0.15.0.0 introduces persistent metadata for reliable upgrades of non-PyPI packages

└──▷ USE IT

Install a package directly from a git repo or local path using the new main argument syntax.

shell

pipx install 'git+https://github.com/user/repo.git'

Inject a dependency specified by version into an existing app, leveraging the new pip spec support.

shell

pipx inject myapp requests>=2.25.0

install command no longer accepts the --spec option; use a valid pip specification as the main argument instead.
inject now accepts pip specifications for dependency arguments, allowing direct reference to package specs without intermediate manifests.

2 details in Everything

└──▷ BREAKING ON UPGRADE

!pipx install no longer accepts the --spec option; users must pass the pip specification as the main positional argument.
!upgrade, upgrade-all, and reinstall-all subcommands have removed options: --spec, --include-deps, --system-site-packages, --index-url, --editable, and --pip-args; these now use original install metadata instead.

0.14.0.0 Aug 11, 2019 · release notes

0.14.0.0 introduces shared venv for performance and renames --include-binaries to --include-apps

Uses a shared virtual environment for pip, setuptools, and wheel to speed up operations

1 detail in Everything

└──▷ BREAKING ON UPGRADE

!The --include-binaries flag in the inject command is renamed to --include-apps

python-pipx

Summary

How python-pipx helps

Languages

Features

What python-pipx offers you

release

docs

release

example

release

docs

release

command line

example

release

docs

release

docs

release

example

docs

release

release

docs

example

release

docs

command line

release

release

docs

release

docs

command line

release

example

release

docs

command line

example

release

docs

command line

release

docs

example

release

docs

release

example

release

release

docs

docs

docs

docs

docs

docs

docs

docs

Command line

Score card

Trajectory

Release-note detail over time

Website history

Rebranding timeline

Releases

Project health

Add the badge to your README