NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI
PyPI, #2120 most downloaded on PyPI
Install and Run Python Applications in Isolated Environments
Latest stable
1.18.18
Last release 5 days ago
17 Nov 2026
Ships on a steady schedule
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
2 versions withdrawn
withdrawn after publishing
9 years old
120 releases · first in 2017
Drag across the ruler to compare, or tap a release to open it.
Pressing Ctrl-C during a command that works on several environments at once, such as pipx upgrade-all , could hang pipx forever; it now stops ( #2473
pipx upgrade-all, could hang pipx forever; it now stops (#2473) by @gaborbernat.Pressing Ctrl-C during a command that works on several environments at once, such as pipx upgrade-all, could hang pipx forever; it now stops (2473) by gaborbernat.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Fix environments created with Python 3.11 failing to start, and pipx commands failing with UnicodeDecodeError , when pipx runs in UTF-8 mode and PIPX_
UnicodeDecodeError, when pipx runs in UTF-8 mode and PIPX_HOME contains non-ASCII characters. pipx writes pipx_shared.pth in the encoding the environment's Python reads it with, and rewrites an existing one the next time it installs into that environment (#2462) by @8hjkkwikl8 and @gaborbernat. (#2460)--pip-args as input errors instead of tracebacks, keeping URL credentials out of the error message (#2439) by @subotac and @gaborbernat.-/_ as the same extra when deciding whether an installed package already satisfies a spec, and when adding extras to a spec (#2463) by @hemtilva.--fetch-python now resumes a standalone Python download when the connection drops before its Content-Length. Before, pipx stopped at the partial archive and failed with a checksum mismatch instead of resuming (#2453) by @HarshJamgaonkar05 and @gaborbernat.pipx execute accepts an app by the suffixed name it has on PATH when its environment was installed with --suffix or its package was injected with --with-suffix, including names that pipx 1.17.14 and earlier exposed with the suffix before the last dot, such as pip3@1.12 (#2468) by @kowellaloo9698-afk.pipx reinstall names pinned packages by environment name rather than path in its error message (#2466) by @kowellaloo9698-afk.pipx uninject also removes the dependencies of the dependencies it removes, including ones that require each other, so uninjecting a package that needs scipy no longer leaves numpy behind (#2442) by @Kernel-Hunter and @gaborbernat.3.16.0a1) under the version number of the final release; fetching a Python that only has prerelease builds fails instead (#2446) by @AP24110011695 and @gaborbernat.pipx environment --value prints an empty line for an unset variable that pipx does not derive, and how to read the effective global paths with --global (#2450) by @xixi-box and @gaborbernat..dist-info/sboms directory, written at build time by python-sbom (#2441) by @gaborbernat.Fix environments created with Python 3.11 failing to start, and pipx commands failing with UnicodeDecodeError, when pipx runs in UTF-8 mode and PIPX_HOME contains non-ASCII characters. pipx writes pipx_shared.pth in the encoding the environment's Python reads it with, and rewrites an existing one the next time it installs into that environment (2462) by 8hjkkwikl8 and gaborbernat. (2460)
Finish updating or rolling back manifest lock files before handling an interrupt, preserving a consistent set of locks (2448) by anticipate218 and gaborbernat.
Report malformed URLs in package specs and --pip-args as input errors instead of tracebacks, keeping URL credentials out of the error message (2439) by subotac and gaborbernat.
Treat extras that differ only in case or in -/_ as the same extra when deciding whether an installed package already satisfies a spec, and when adding extras to a spec (2463) by hemtilva.
--fetch-python now resumes a standalone Python download when the connection drops before its Content-Length. Before, pipx stopped at the partial archive and failed with a checksum mismatch instead of resuming (2453) by HarshJamgaonkar05 and gaborbernat.
pipx execute accepts an app by the suffixed name it has on PATH when its environment was installed with --suffix or its package was injected with --with-suffix, including names that pipx 1.17.14 and earlier exposed with the suffix before the last dot, such as pip3@1.12 (2468) by kowellaloo9698-afk.
pipx reinstall names pinned packages by environment name rather than path in its error message (2466) by kowellaloo9698-afk.
pipx uninject also removes the dependencies of the dependencies it removes, including ones that require each other, so uninjecting a package that needs scipy no longer leaves numpy behind (2442) by Kernel-Hunter and gaborbernat.
pipx no longer installs a python-build-standalone prerelease (such as 3.16.0a1) under the version number of the final release; fetching a Python that only has prerelease builds fails instead (2446) by AP24110011695 and gaborbernat.
Document that pipx environment --value prints an empty line for an unset variable that pipx does not derive, and how to read the effective global paths with --global (2450) by xixi-box and gaborbernat.
Every wheel now carries a PEP 770 CycloneDX SBOM in its .dist-info/sboms directory, written at build time by python-sbom (2441) by gaborbernat.
pipx ensurepath no longer claims it added the binary directories to PATH when they were already there; the summary now says so and points at --force f
pipx ensurepath no longer claims it added the binary directories to PATH when they were already there; the summary now says so and points at --force for adding them again (#2431) by @AP24110011695 and @gaborbernat.pipx ensurepath no longer claims it added the binary directories to PATH when they were already there; the summary now says so and points at --force for adding them again (2431) by AP24110011695 and gaborbernat.
Rebuild shared pip environments created with Python older than 3.10, and refresh existing applications' references to the rebuilt environment before running their installers (2437) by gaborbernat. (2435)
pipx pin --skip accepts case and punctuation variants of injected package names, with or without their suffix ( #2425 ) by @kowellaloo9698-afk and @ga
pipx pin --skip accepts case and punctuation variants of injected package names, with or without their suffix (#2425) by @kowellaloo9698-afk and @gaborbernat.pipx repair now refuses an environment whose pipx_metadata.json a killed install lost or a newer pipx wrote, as pipx reinstall and pipx reinstall-all do, instead of reporting it healthy (#2423) by @AP24110011695 and @gaborbernat.pipx pin --skip accepts case and punctuation variants of injected package names, with or without their suffix (2425) by kowellaloo9698-afk and gaborbernat.
pipx repair now refuses an environment whose pipx_metadata.json a killed install lost or a newer pipx wrote, as pipx reinstall and pipx reinstall-all do, instead of reporting it healthy (2423) by AP24110011695 and gaborbernat.
pipx list --short --include-injected now lists injected packages, as --pinned --include-injected already does ( #2415 ) by @Pixeless001 and @gaborbern
pipx list --short --include-injected now lists injected packages, as --pinned --include-injected already does (#2415) by @Pixeless001 and @gaborbernat.pipx uninject matches package names in any spelling, so mixed-case finds a package that pip recorded as Mixed_Case, and it refuses the main package however the name is spelled (#2420) by @guransh0925 and @gaborbernat.pipx list --short --include-injected now lists injected packages, as --pinned --include-injected already does (2415) by Pixeless001 and gaborbernat.
pipx uninject matches package names in any spelling, so mixed-case finds a package that pip recorded as Mixed_Case, and it refuses the main package however the name is spelled (2420) by guransh0925 and gaborbernat.
No user-facing changes. 🐍 PyPI release 📜 Full Changelog
pipx run now treats requirements with a version, extras, a marker or a direct URL as packages, and script URLs as downloads, even when the working dir
pipx run now treats requirements with a version, extras, a marker or a direct URL as packages, and script URLs as downloads, even when the working directory contains a matching file (#2408) by @gaborbernat.pipx run now treats requirements with a version, extras, a marker or a direct URL as packages, and script URLs as downloads, even when the working directory contains a matching file (2408) by gaborbernat.
Fetch fresh standalone Python release data when the cached index is invalid or unreadable ( #2404 ) by @hemcharan710-afk and @gaborbernat .
pipx pin now lists the packages it pins without --injected-only or --skip (#2405) by @hemcharan710-afk and @gaborbernat.Fetch fresh standalone Python release data when the cached index is invalid or unreadable (2404) by hemcharan710-afk and gaborbernat.
pipx pin now lists the packages it pins without --injected-only or --skip (2405) by hemcharan710-afk and gaborbernat.
Error, warning, and help messages now state what pipx found and what to run next, without hedges such as "already seems to be installed" or "Perhaps".
pipx upgrade pipx or pipx reinstall pipx for example, no longer crashes with an ImportError when another pipx command empties the trash while it is still running, such as during the rest of pipx upgrade-all. The copy of its environment it imports from now stays in the trash until the process exits (#2397) by @gaborbernat.pipx reinstall-all with Ctrl-C now gives a restored environment back the shared app, man page or completion links another environment took while the rebuild had it in the trash, as a failed rebuild already did (#2386) by @gaborbernat.pipx run --refresh or --no-cache of a local script no longer deletes the cached environment while another run of the same script is still executing in it, and neither does the expiry sweep. Such a run builds a throwaway environment for itself instead, and after --refresh the next run to find the cached one idle rebuilds it (#2387) by @gaborbernat.pipx upgrade pipx on a pipx that manages itself no longer fails with Access is denied and rolls back. uv deletes the files it replaces, which Windows refuses for the running pipx.exe, so pipx now moves that launcher to its trash first, where the next pipx command deletes it (#2396) by @gaborbernat.pipx reinstall and pipx install --force no longer warn Overwriting file for the package's own launcher. Windows .exe launchers embed their build time, so a rebuilt one never matched its old copy byte for byte and every reinstall warned. pipx now recognises its own copy by the interpreter it names and replaces it without a warning; a file another venv or the user put there still gets one (#2394) by @gaborbernat.UV_LINK_MODE=symlink, pipx uninstall now removes the man page and shell completion links it exposed, and pipx list no longer reports those man pages as missing. uv makes the environment's own copies symlinks into its cache, and pipx followed them there instead of stopping at the environment (#2380) by @gaborbernat.--fetch-python and pipx interpreter upgrade now download and unpack the standalone Python build next to the interpreter directory instead of in the system temp dir, so a tmpfs /tmp or a /tmp on another btrfs subvolume no longer forces a full copy of the build into the pipx home or splits its hard links into separate files (#2403) by @gaborbernat.pipx inject pipx without --include-apps and pipx runpip pipx on a pipx that manages itself no longer mix old and new pipx code when they change the pipx package. Like pipx upgrade pipx, they now load late imports from a copy of the environment, which the next pipx command deletes from the trash (#2393) by @gaborbernat.pipx list --json no longer exports the interpreter a self-managed pipx recorded when that path no longer leads to the interpreter its environment runs on, such as a removed bootstrap environment's python3. pipx install-all then builds that environment on the default interpreter instead of whatever appears at the old path (#2389) by @gaborbernat.pipx reinstall pipx on a pipx that manages itself no longer crashes with an ImportError when it installs a different pipx version. Modules the running pipx imported late came from the version it was installing, so old and new code mixed. It now loads them from its own moved environment, which the next pipx command deletes from the trash (#2377) by @gaborbernat.pipx upgrade pipx, pipx upgrade-all and pipx install --force pipx on a pipx that manages itself no longer crash with an ImportError when they install a different pipx version. The running pipx now loads its late imports from a copy of its environment, which the next pipx command deletes from the trash (#2388) by @gaborbernat.#!/bin/sh line that hands over to the interpreter, and pipx took /bin/sh for the interpreter, so pipx reinstall kept a stale copy and warned "File exists ... Not modifying." (#2392) by @gaborbernat.pipx run now names its cached environments with an HMAC keyed by a random per-user secret, stored with mode 0600 in .run-key inside the run cache. Before, the name was a plain hash of inputs that include tokens and proxy passwords from the environment, so another account that could list the cache could check guesses at those values against it. Existing cache entries are not reused and expire as usual (#2370) by @gaborbernat.--requirem FILE, which pip 24.0 reads as --requirement FILE. With such a shared pip, a later pipx upgrade or pipx reinstall used to replay it and install from whatever another account had put at that path. An existing record drops it when read, and an abbreviation that could name a source option such as --constraint goes through the same replay check as that option (#2390) by @gaborbernat.python3 of an activated bootstrap environment or of one made with python3 -m venv --copies. It records the base interpreter named in that environment's pyvenv.cfg, which outlives the bootstrap. pipx install-all also stops building on an exported interpreter that sits inside a virtual environment or that another account can change, and uses the default Python with a message instead, so a snapshot taken before the bootstrap was removed no longer runs whatever another account later puts at its old path (#2402) by @gaborbernat.Extend the 1.18.8 handling of recorded pip arguments to uv's path options and to --group . pipx no longer records --group , which names a pyproject.to
--group. pipx no longer records --group, which names a pyproject.toml to read packages from, like -r. On POSIX, a recorded --config-file, --project, --directory, --overrides/--override or --excludes/--exclude that points at a path another account could change stops pipx upgrade, pipx reinstall and the other replaying commands with the same error as --find-links. pipx list --outdated runs the same check and reports such an environment as failed instead of querying the recorded location. pipx runpip reads its install arguments with the same parser, so it records an install written as -qe ./project or -e./project as editable (#2363) by @gaborbernat.pipx reinstall-all, the restored environment gets back the shared app, man page or completion links another environment took while the rebuild had it in the trash, unless something outside this run has replaced them since (#2371) by @gaborbernat.pipx run no longer reuses a cached environment after a change to a variable outside PIP_* and UV_* that decides which config file pip or uv reads, which proxy or index answers, which certificate is trusted or which credentials are sent, such as XDG_CONFIG_HOME, SSL_CERT_FILE, HTTPS_PROXY or NETRC. The values only feed the cache key's hash, so secrets in them stay out of cache paths and logs (#2364) by @gaborbernat.Document what the security policy covers: which inputs pipx trusts, and which reports count as vulnerabilities (#2198) by @gaborbernat.
<a name="release-1-18-8-fixed"></a>
pipx run that names an app the package does not provide, such as pipx run --spec black blackk, no longer expires the cached environment, so the corrected command reuses it instead of rebuilding. A failed venv creation or install still expires the entry (#2354) by @gaborbernat.pipx reinstall-all, upgrade-all or install-all no longer hangs pipx. A signal handled just after a worker took the shared lock could leave it held, so every other task waited forever (#2348) by @gaborbernat.python3 of a bootstrap environment removed after pipx install pipx --python python3. pipx failed every command with a PIPX_DEFAULT_PYTHON error, or built new environments on whatever appeared at that path later (#2245) by @gaborbernat.--cooldown and PIPX_COOLDOWN to the shared pip that the pip backend installs or refreshes during the command. pipx used to fetch the newest pip, even one uploaded minutes earlier, while it held back the package itself. A new shared environment now starts from the oldest pip pipx supports and upgrades only to a release older than the cooldown (#2311) by @gaborbernat.SIGTERM or SIGHUP arrives while a failed or interrupted pipx reinstall, install --force, inject, upgrade or manifest sync rolls it back. The rollback deletes the half-built environment and then moves the backup in, and a signal between the two steps left the environment deleted and its only copy in the trash, which the next pipx command emptied. pipx now holds such a signal until the backup is back in place and acts on it afterwards (#2329) by @gaborbernat... and symlinks, and a wheel installed by name could ship its own editable direct_url.json to make pipx copy any readable file into the environment and link it as a man page (#2268) by @gaborbernat..., and never delete a directory to make room for an app link, so pipx reinstall can no longer remove the parent of PIPX_BIN_DIR (#2228) by @gaborbernat.venv_args other than --system-site-packages, with a warning, when reading a snapshot or pipx_metadata.json, so pipx install-all and pipx reinstall no longer pass an edited --clear <dir> or an extra directory to python -m venv (#2239) by @gaborbernat.pipx reinstall-all, upgrade-all, and install-all waiting for the environments they change when pipx can no longer write their output, as with pipx reinstall-all 2>&1 | head or a closed stderr. pipx used to log a traceback and return while it still rebuilt environments in the background, so an interrupt then skipped the rollback, and an environment waiting for its turn hung (#2290) by @gaborbernat.pipx reinstall, reinstall-all, uninject or uninstall-all was running. These commands gathered the environment's links first and deleted them by name later, so a name another package claimed in between, for example in the same parallel reinstall-all, disappeared without a message. pipx now deletes a link only if it still points into the environment by Bernát Gábor.pipx_metadata.json when the installer replaces it with a wheel's data file of the same name. A failed pipx install --force, pipx upgrade or pipx inject, or a pipx runpip APP install of a dependency, used to leave the wheel's copy in place, and later commands read its index arguments, spec and suffix as pipx's own. pipx now puts its record back after every installer run (#2269) by @gaborbernat.tarfile.data_filter. pipx's own extractor checked member names as text, so a member whose path went through a symlink unpacked earlier from the same archive was written wherever that link led. It now resolves each path through the links already on disk, extracts under normalized names like the data filter does, and refuses a hard link to a symlink (#2279) by @gaborbernat.pipx manifest sync reinstalls an existing environment, and expose the environment again when the sync is interrupted. pipx used to drop those links without a message, so another package could take the freed names without --force, and an interrupted sync left the rolled-back environment unexposed (#2273) by @gaborbernat.pipx install --force or pipx install-all --force cannot move it aside before a Requires-Python rebuild. On Windows the move fails while any file inside the environment is open, and pipx then deleted the environment and reported a FileNotFoundError instead of the real error. pipx now retries the move the way pipx reinstall does, and if it still fails it leaves the environment in place and reports the original error (#2350) by @gaborbernat.pipx runpip <venv> install abbreviates a value-taking pip option whose value names the package, such as --only-bin <name> for --only-binary <name>, and record an install through an abbreviated --editable, such as --edit <path>, as editable (#2225) by @gaborbernat.pipx reinstall, reinstall-all, install --force, upgrade or inject when another pipx command starts. Every command used to empty the trash at startup, so a pipx list run meanwhile deleted the backup, and when the first command then failed or was interrupted it lost the environment with a FileNotFoundError. pipx now skips a backup while its environment's lock is held and removes it only once orphaned (#2298) by @gaborbernat.pipx reinstall, reinstall-all, interpreter upgrade, the repair step of pipx upgrade, or a repeated pipx manifest sync rebuilds the environment. These used to replace such a file as if --force had been passed, deleting a user's own script or repointing another environment's command, although pipx install had left it alone with a warning. A name two environments both declare now stays with the one that held it, instead of going to whichever reinstall-all rebuilt last (#2321) by @gaborbernat.pipx install-all without --force. pipx said it was not modifying the environment, then injected the snapshot's injected_packages into it anyway. Pass --force to bring existing environments in line with the snapshot (#2333) by @gaborbernat.--force cleared. A link counts as left over when the environment it points into no longer lists the file in its metadata. The collision warning for a link whose target is missing now says so (#2356) by @gaborbernat.Injecting packages log line, the --output json error fields of inject, install and uninject, the progress lines of pipx run script dependencies and --preinstall, the local source that pipx upgrade reports, invalid requirement errors from manifests and inline script metadata, --pip-args rejected by the uv backend of pipx run, the "looks like a path" error, and installer output that pipx captures and logs (#2252) by @gaborbernat.--index-url "http://alice:correct horse@host/simple", in the command log, --verbose output and messages; pipx now masks each argument of a command line before joining it (#2241) by @gaborbernat.https://TOKEN:@host or TOKEN:x-oauth-basic@ no longer shows in the command log, --verbose output and messages. Such URLs now show as ****:****@, which also hides a plain user name such as alice (#2244) by @gaborbernat.pipx run script.py now releases the run-cache lock before the script starts. pipx held it until the script exited, so a second run of the same script waited without a message, and a script that ran itself through pipx never finished (#2352) by @gaborbernat.pipx install --lock and pipx manifest sync with a lock under the pip backend when the environment's pip is older than 26.1. That pip read pylock.toml as a requirements file: a real lock failed with a confusing Invalid requirement error, and a file that was not a lock had its lines applied as pip options. The error now names the pip version and suggests pipx upgrade-shared (#2289) by @gaborbernat.METADATA names a different project than its .dist-info directory. A wheel could rewrite that name through its data files and make pipx install --upgrade URL install it into another application's environment (#2236) by @gaborbernat.--python value that is not a version before --fetch-python=missing or --fetch-python=always looks in the standalone interpreter cache. pipx joined the raw value onto PIPX_HOME/py and deleted the result as a failed earlier download, so a directory path, .., . or a bare python removed that directory, PIPX_HOME or the whole interpreter cache (#2262) by @gaborbernat.--index-url instead of silently installing from the default index (#2217) by @Svastikkka.--pip-args (--index-url, -i, --extra-index-url, --default-index, --index), and under the uv backend an empty index recorded by an earlier install, instead of letting uv install from the default index (#2253) by @gaborbernat.$PIPX_HOME/venvs. pipx uninstall "", for example from an unset shell variable, used to remove every environment and exit 0, and an install-all snapshot, manifest tool name or reported package name holding a path built the environment at that path. pipx now stops with Invalid environment name (#2331) by @gaborbernat./etc/profile.d/pipx.sh or /etc/paths.d/pipx in pipx ensurepath --global when the file holds content pipx did not write, such as an administrator's PIPX_GLOBAL_HOME or PIP_INDEX_URL exports. pipx used to replace the whole file with its PATH entry and report success. It now leaves the file and its mode alone and exits with an error that names --force, which still replaces the file. pipx replaces a file that holds only an earlier pipx entry, as before (#2315) by @gaborbernat.pipx manifest lock when a tool's lock path resolves outside the manifest directory, instead of replacing a pylock.toml elsewhere on disk and discarding its previous contents. pipx manifest sync still reads such locks (#2223) by @gaborbernat.pyvenv.cfg is gone, and suggest pipx reinstall. Without that file the environment's python link starts the interpreter it was created from, so a pipx upgrade after a wheel had shipped and then dropped pyvenv.cfg installed the package into that interpreter's prefix and reported success (#2326) by @gaborbernat.--global, --skip-maintenance, --verbose and --quiet placed between manifest, interpreter or cache and their subcommand, as in pipx manifest --global sync. pipx accepted the option there and then dropped it, so pipx manifest --global sync --prune synced and pruned the per-user store with exit 0. Put the option after the subcommand, as in pipx manifest sync --global (#2320) by @gaborbernat.pipx_metadata.json the current user cannot read as unreadable in pipx list, instead of as missing metadata from a pipx older than 0.15 that needs reinstalling. A non-root user sees this for every environment of pipx list --global, because pipx keeps the file owner-only: it can hold index credentials. pipx list still lists the environments the user can read (#2323) by @gaborbernat.--cert ca.pem, -r requirements.txt, --log or --cache-dir, against the directory pipx was started in, also when the option is clustered or abbreviated, as in -qr requirements.txt or --find-l wheels. The shared pip refresh runs inside the shared libraries directory, so pipx upgrade-shared --pip-args='--cert=ca.pem' failed with invalid path: ca.pem; installs, upgrades and pipx run now also resolve these values against the starting directory (#2351) by @gaborbernat.pipx manifest lock fails because a directory sits at a later tool's lock path. pipx used to stop rolling back at that directory, keep the new locks of the tools before it, and delete their previous versions (#2260) by @gaborbernat.pipx install --force or pipx install-all --force rebuilds it on another interpreter because of the package's Requires-Python and the rebuild fails. pipx used to delete the environment first and leave behind an empty one without its app, injected packages, or pipx_metadata.json, while it reported it had kept the environment. It now moves the environment to its trash before the rebuild and moves it back on failure (#2229) by @gaborbernat.pipx ensurepath --global --force from crashing with UnicodeDecodeError when /etc/profile.d/pipx.sh or /etc/paths.d/pipx holds bytes that are not UTF-8. --force now replaces the file without reading it, and without --force such a file gets the same error that names --force as any other file pipx did not write (#2355) by @gaborbernat.pipx interpreter upgrade from moving an environment to another Python found on PATH when the newest release of its package has a Requires-Python that rules out the new standalone build. The command reported the patch upgrade as done while the environment now ran on, for example, /usr/bin/python3.11. It now fails, restores the environment on its standalone build, and exits 1 (#2301) by @gaborbernat.pipx upgrade-all from moving an app, manual page, or completion that two environments expose to the other environment while the installer of its owner is replacing the linked file. pipx treated any link whose target was missing as left over and replaced it without --force; a missing target inside another environment that still exists now counts as a collision (#2303) by @gaborbernat.pipx install pipx) started through its own environment's script from taking that environment's bin directory for PIPX_BIN_DIR when the path to the script holds .. or a symlinked directory, such as ../share/pipx/venvs/pipx/bin/pipx from ~/.local/bin. Such a command linked the apps it installed into pipx's own environment, off PATH and onto pipx's own import path. pipx now recognizes the exposed link by real locations, which also works when you reach the pipx home through a symlink (#2309) by @gaborbernat.python -m pipx, once pipx.__main__ starts. After pip install --user pipx that directory is ~/.local/bin, where pipx links apps, so pipx imported a json.py or shlex.py script a package shipped there in place of the standard library module, and an exposed json.py broke every later pipx command, pipx uninstall included. For modules pip's launcher imports before that point, such as re and enum, pipx refuses to expose apps named after standard library modules. Programs that import pipx.__main__ no longer see their script directory on sys.path either (#2316) by @gaborbernat.-r requirements.txt, --log, --report, --cache-dir or --target: they apply to the command they were given on, and a later pipx upgrade or pipx reinstall no longer reads or writes those paths. pipx reads pip arguments as pip does, so a clustered short option such as -qr requirements.txt or an abbreviation such as --log-f pip.log counts too. On POSIX, pipx upgrade, pipx reinstall and the other commands that replay recorded arguments stop with an error, before the installer runs and without changing the record, when a recorded --find-links, --constraint, --build-constraint, --cert, --client-cert, or file:// or local-path index URL points at a path another account could change. Pass the options again with --pip-args to use them for that run (#2359) by @gaborbernat.PIPX_HOME/py. Both staged the build in one fixed directory and each deleted the other's half-copied tree as a leftover; pipx now holds a per-version lock while it fetches, so the second command waits and reuses the first one's build. pipx interpreter list, prune and upgrade also skip the staging and backup directories of a fetch in progress instead of treating them as interpreters. An interpreter that an earlier fetch already left incomplete still needs deleting by hand (#2293) by @gaborbernat.pip.conf (pip.ini on Windows) from the root of an environment before it starts pip there. A wheel could ship that file as a data file, and pip read it as its site configuration, so a target or index in it made a later pipx upgrade or pipx inject install outside the environment or from another index (#2264) by @gaborbernat.--index-url (-i) now reaches uv as --default-index. uv let UV_DEFAULT_INDEX or a default [[index]] entry override a command-line --index-url, so pipx run, install, upgrade and outdated used the default index instead of the one named on the command line (#2247) by @gaborbernat.pipx run script.py now keeps the script's environment in pipx's run cache, keyed to the script's path, the interpreter, --pip-args and the cooldown. uv kept one environment per script path and reused it while it satisfied the script, so a changed --index-url, --pip-args or --cooldown, or --refresh, still ran what an earlier run installed. pipx cache purge and the 14-day expiry now cover these environments (#2274) by @gaborbernat.pipx run now puts -- before the app name it hands to uv tool run. An app word that started with a single dash, such as pipx run -- -ihttp://host/simple demodep, was read by uv as one of its own options, and uv installed and ran the next word as the package (#2299) by @gaborbernat.pipx upgrade, upgrade-all and install --upgrade now pass uv --upgrade-package NAME instead of --upgrade, so they upgrade only the named package and leave its dependencies alone unless the new release needs others, as pip's default only-if-needed strategy does. Before, uv upgraded every dependency, replacing packages injected with pipx inject --force and pinned with pipx pin --injected-only (#2248) by @gaborbernat.pipx install or pipx run --spec under the pip backend has to install a URL, VCS or sdist spec to learn its name, the shared pip it installs along the way now comes from the command's --index-url and --pip-args instead of pip's default index (#2275) by @gaborbernat..dist-info records with the same name, pipx now reads the first one on sys.path, the one the environment's interpreter uses. Since 1.15.1 it read the last one, so --system-site-packages with a different version of the package in the base interpreter reported that version and exposed its commands (#2258) by @gaborbernat.pipx install --preinstall and pipx run --with now refuse a value that starts with -. Written as --with=--find-links=DIR or --preinstall=-rFILE, such a value reached pip or uv pip install as an installer option and changed where packages came from, instead of failing like the main package spec does. Pass installer options with --pip-args (#2307) by @gaborbernat.pipx install-all --backend uv now translates index options that a pip recording spells as an abbreviation pip accepts, such as --index-u URL, instead of dropping them and installing from the default index. A recorded pip --index URL now becomes uv --default-index URL, matching how pip read it (#2232) by @gaborbernat.pipx install with several packages no longer builds every environment on the Python it picked for one package whose Requires-Python rules out the default interpreter; the other packages keep the default Python (#2222) by @gaborbernat.pipx list --outdated and pipx upgrade-all now check uv environments against the index recorded with uv's option names (--default-index, --index, --allow-insecure-host, --index-strategy, --keyring-provider) instead of uv's default index (#2220) by @gaborbernat.pipx reinstall, pipx reinstall-all and pipx repair now refuse an environment whose pipx_metadata.json is unreadable or was lost to a killed install, instead of rebuilding it from the default index under the directory name. pipx install marks the environment unfinished until it writes the record, and pipx uninstall moves the environment to its trash before deleting it, so a killed uninstall no longer leaves a venv without its record (#2234) by @gaborbernat.pipx run --with now installs the --with packages in the same installer call as the app. pipx skipped a --with naming a package the app already depends on, such as --with 'dep==1.0', as already installed, so the app ran with the newest release on the pip backend. A --with naming the app with an extra no longer links the cached environment's commands into PIPX_BIN_DIR (#2266) by @gaborbernat.pipx run script.py now expires its cache entry when creating the environment fails or is interrupted, not only when installing the script's dependencies does. A Ctrl-C during python -m venv left an empty cache directory, and every later run of the script reused it and failed with FileNotFoundError until the entry expired (#2294) by @gaborbernat.pipx run and pipx install now fail when a script download ends before its Content-Length. Before, pipx ran or installed the part that arrived and could exit 0 (#2251) by @gaborbernat.pipx run and pipx install now refuse an http or https script URL with credentials, naming it with the password masked. Before, a URL such as https://user:password@host/tool.py failed with an error that printed the password in clear text and wrote it to the log. pipx install also reports a malformed script URL as an error instead of a traceback (#2249) by @gaborbernat.pipx run no longer keys its cache on the PIP_* and UV_* variables that cannot change what the installer resolves or installs: timeouts, retries, parallelism, verbosity, progress and color output, cache directories, and the UV_RUN_RECURSION_DEPTH that uv run sets for its children. Setting one of them rebuilt the environment for an unchanged command. Every other variable with those prefixes stays in the key, whatever its case or -/_ spelling, since pip reads PIP_index_url the same as PIP_INDEX_URL (#2353) by @gaborbernat.pipx run now includes the installer's environment variables (PIP_*, or UV_* under the uv backend) in its cache key. A run after changing PIP_INDEX_URL, PIP_FIND_LINKS or UV_INDEX_URL reused the environment built from the previous index for up to 14 days (#2282) by @gaborbernat.pipx run now keys its cache on the absolute path of a local --spec, --with or --find-links value. The same relative path typed in two directories, such as --spec ./dist/tool-1.0-py3-none-any.whl, shared one environment, so the second directory ran the first directory's build by Bernát Gábor.pipx run now names the script URL, with credentials masked, when a download fails, as pipx install already did. pipx install of a script URL whose body does not decode in its declared charset, or declares an unknown one, now reports an error instead of a traceback, as pipx run already did (#2255) by @gaborbernat.pipx runpip <venv> install now records a relative --find-links (-f) path resolved against the directory you ran it from. Before, a later pipx upgrade or pipx reinstall read it against the environment's directory, failed with Failed to read --find-links directory or No matching distribution found, and rolled back (#2349) by @gaborbernat.pipx runpip starts pip or uv in your working directory again instead of the environment's root, so relative paths such as -r requirements.txt, -c constraints.txt or ./dist/app.whl name your files. Since 1.12.0 the installer looked them up in the environment, where they were missing or named a data file an installed wheel had put there (#2318) by @gaborbernat.pipx uninject no longer removes apps, man pages and completions that the main package or another injected package of the environment still exposes, such as a command of a dependency both packages share under --include-deps (#2296) by @gaborbernat.pipx uninject now ignores installed distributions whose metadata Name is not a valid project name when it looks for orphaned dependencies to remove. A name such as -t/some/dir or -rFILE reached uv pip uninstall or pip uninstall as an option, and with uv could delete packages from a directory outside pipx (#2306) by @gaborbernat.installed-files.txt lists a looping symlink, and skips that entry instead (#2336) by @gaborbernat.pipx plus an import suffix, such as enum.py, re.pyc or pipx.py, or a directory named after one, and warns instead. Python searches the directory of the script it starts first, so in ~/.local/bin such an app replaced the module for pip's pipx launcher, which imports re and then pipx before pipx can drop that directory from sys.path, and for every other Python script installed there (#2342) by @gaborbernat.installed-files.txt from a distribution that has a RECORD, matching importlib.metadata. A dependency, or a package injected without --include-apps, could ship that file into the main package's .dist-info and get its own apps, man pages and completions exposed without --include-deps (#2277) by @gaborbernat.-E to an app script's shebang by writing a new file and renaming it over the script, instead of writing into the existing file. With the uv backend the script can be a hard link or symlink into uv's cache, so the in-place write also changed the cache entry and the same script in every other environment uv had installed that wheel into (#2285) by @gaborbernat.entry_points.txt only when that package's RECORD lists it, or when the package has no RECORD. A dependency could ship that file into the .dist-info of a main package that has no entry points of its own and get its apps exposed without --include-deps (#2340) by @gaborbernat.<a name="release-1-18-8-documentation"></a>
<a name="release-1-18-8-security"></a>
pipx install pycowsay now always means the package on the index. A file of that name without a suffix in the working directory no longer gets installed as a PEP 723 script; pass a path such as ./pycowsay to install one. URL specs no longer pick up a script at the matching relative path below the working directory either (#2243) by @gaborbernat.--python value only when it is an X or X.Y version. The launcher ran any other value, such as 3.14.8 or 3.13t, on the first interpreter its search found, which could be a .venv in a parent of the current directory (#2242) by @gaborbernat.mktemp -d instead of the fixed /tmp/bootstrap path, which another local user could create first and plant code in that ran as the reader, and as root at the sudo step (#2219) by @gaborbernat.PIPX_DEFAULT_PYTHON, such as python3, on PATH only: pipx no longer uses a file of that name in the current directory as the default interpreter. Write ./python3 to pick that file on purpose (#2226) by @gaborbernat.PATH lookup found for --python python3.11 on to the backend instead of the bare name. uv read the bare name as a version request and could pick a .venv interpreter from a parent of the current directory. A file in the current directory named like the value, such as ./3.11, no longer counts as a path either (#2240) by @gaborbernat.pyproject.toml or wheel only for local path specs. A URL spec such as https://host/app.whl no longer takes its name, and with it the target environment, from a file at the matching relative path below the working directory (#2238) by @gaborbernat.--find-links and --constraint values passed to pipx upgrade --pip-args and pipx run scripts as absolute paths, resolve relative values already in pipx_metadata.json against the environment's directory, and run the shared pip refresh inside the shared libraries directory, so a later pipx upgrade or pipx reinstall no longer reads wheels from whatever directory you start it in (#2233) by @gaborbernat.pipx runpip <venv> install that replaces the main package, so a later pipx upgrade or pipx reinstall asks the same index instead of resolving the bare name on the default one (#2231) by @gaborbernat.pipx.run entry points, and apps run with --python-args with python -P so a module in the current directory, such as a planted json.py, no longer shadows what the program imports (#2221) by @gaborbernat.pipx reinstall from replacing the main package while it replays injected packages. The replay passed --force-reinstall, so an injected package that depends on the main package made the installer fetch the main package again by name from the injected package's index and install that release over the recorded source. pipx inject --force now passes --force-reinstall only when the package is already injected, and under the uv backend reinstalls just that package with --reinstall-package (#2227) by @gaborbernat.pipx run from retrying a failed uv install with pip. A venv directory without pipx_metadata.json no longer counts as recorded with the pip backend, so it resolves its backend like a new venv, and a pipx run whose install fails now expires its cache entry so the next run rebuilds it. pip ignores UV_INDEX_URL, so the retry fetched the package from pip's default index instead of the private one (#2235) by @gaborbernat.uv.toml or pyproject.toml found in the directory uv runs in, the script's directory, or their parents, such as one another local account wrote to a shared /tmp. pipx now points uv's project-config search at PIPX_HOME through UV_PROJECT, and through --project for uv run --script. Your user and system uv.toml and UV_CONFIG_FILE still apply. Keep PIPX_HOME out of directories other accounts can write (#2246) by @gaborbernat.pipx install --force or pipx manifest sync rebuilds an existing environment, either on another Python because the release's Requires-Python rules out the current one or to apply a lock file, keep the backend recorded for that environment. The rebuild used to pick the backend as for a new environment, so a pip-backed environment could move to uv and install from uv's default index instead of the one set in PIP_INDEX_URL or pip.conf (#2237) by @gaborbernat.pipx inject ENV 'APP[extra]' now adds the extra to the main package's recorded source instead of replacing it with the bare name APP[extra]. An app installed from a wheel, a directory or a URL no longer turns into the index's project of the same name on the next pipx upgrade or pipx reinstall. Extras accumulate with the ones already recorded, and a main-package spec that changes the version, path or URL needs --force (#2250) by @gaborbernat.pipx manifest sync now keeps the installer and venv options recorded for an environment that already exists, such as --index-url. It used to reinstall the tool from the default index and erase the recorded options (#2224) by @gaborbernat.0700), tightens an existing one, and writes cmd_*.log and cmd_*_{pip,uv}_errors.log as 0600. The logs record the full command line, including the arguments pipx run and pipx exec pass to the application, and in a --global store under /opt/pipx/logs any local account could read them (#2230) by @gaborbernat.Require pip 26.2.2 or later in the shared libraries, and replace an older shared pip on the next pipx command instead of waiting for the 30-day refres
<a name="release-1-18-7-security"></a>
Require pip 26.2.2 or later in the shared libraries, and replace an older shared pip on the next pipx command instead of waiting for the 30-day refresh. Older pip releases bundle a certifi that still trusts the compromised eMudhra/emSign root CA (2197) by gaborbernat.
Keep the extras on a local archive named without ./, so pipx install "tool-1.0-py3-none-any.whl[cow]" installs the cow extra like ./tool-1.0-py3-none-
<a name="release-1-18-6-fixed"></a>
./, so pipx install "tool-1.0-py3-none-any.whl[cow]" installs the cow extra like ./tool-1.0-py3-none-any.whl[cow] does. A version specifier, URL or environment marker after such a name now fails with an error instead of being silently dropped (#2174) by @Cyber-Marty and @gaborbernat.pipx runpip <venv> install passes an option value that names the package, such as --only-binary <name>, --no-binary <name>, or uv's --upgrade-package <name> (#2166) by @dailyun and @gaborbernat.# /// line, instead of failing with Unterminated string. As the inline script metadata specification requires, the block now ends at the last # /// line of its comment run (#2172) by @zurrll and @gaborbernat.--include-deps (#2185) by @JackyHsu-X and @gaborbernat.pipx install pkg-1.0.tar.xz and other bare filenames ending in an archive extension pip accepts (.tar.bz2, .tgz, .tar and the rest, in any letter case) now install the local file instead of looking up a mangled project name on PyPI (#2177) by @ShahabAhmed01 and @gaborbernat.pipx upgrade-all --pip-args=--index-url, or any other index option given without a value, now fails with an error naming the option instead of a StopIteration traceback, and --output json reports it in the usual error envelope (#2182) by @jdotc1 and @gaborbernat.<a name="release-1-18-6-documentation"></a>
Keep the extras on a local archive named without ./, so pipx install "tool-1.0-py3-none-any.whl[cow]" installs the cow extra like ./tool-1.0-py3-none-any.whl[cow] does. A version specifier, URL or environment marker after such a name now fails with an error instead of being silently dropped (2174) by Cyber-Marty and gaborbernat.
Keep the recorded source of a local wheel when pipx runpip <venv> install passes an option value that names the package, such as --only-binary <name>, --no-binary <name>, or uv's --upgrade-package <name> (2166) by dailyun and gaborbernat.
Read the full inline script metadata block when a TOML multiline string in it contains a # /// line, instead of failing with Unterminated string. As the inline script metadata specification requires, the block now ends at the last # /// line of its comment run (2172) by zurrll and gaborbernat.
Retain commands enabled by additional dependency extras with --include-deps (2185) by JackyHsu-X and gaborbernat.
pipx install pkg-1.0.tar.xz and other bare filenames ending in an archive extension pip accepts (.tar.bz2, .tgz, .tar and the rest, in any letter case) now install the local file instead of looking up a mangled project name on PyPI (2177) by ShahabAhmed01 and gaborbernat.
pipx upgrade-all --pip-args=--index-url, or any other index option given without a value, now fails with an error naming the option instead of a StopIteration traceback, and --output json reports it in the usual error envelope (2182) by jdotc1 and gaborbernat.
Fix the dead PythonBytes episode link on the docs home page (2170) by qodelicious and gaborbernat.
Use a current black commit in the install-from-commit example (2181) by dcadolph and gaborbernat.
Releases now run on the shared tox-dev/github-workflows pipeline, with a locked release toolchain and generated GitHub Release notes (#2190) by @gabor
<a name="release-1-18-5-packaging"></a>
Releases now run on the shared tox-dev/github-workflows pipeline, with a locked release toolchain and generated GitHub Release notes (2190) by gaborbernat.
pipx reset now cancels instead of crashing when the confirmation prompt reads EOF (Ctrl-D on POSIX, Ctrl-Z then Enter on Windows). (#2160) by @XXXXXQ-
<a name="release-1-18-4-fixed"></a>
pipx reset now cancels instead of crashing when the confirmation prompt reads EOF (Ctrl-D on POSIX, Ctrl-Z then Enter on Windows). (#2160) by @XXXXXQ-0206 and @gaborbernatpipx reset now cancels instead of crashing when the confirmation prompt reads EOF (Ctrl-D on POSIX, Ctrl-Z then Enter on Windows). (2160) by XXXXXQ-0206 and gaborbernat
Allow selecting dependencies that ship only shell completions. (#2157) by @AryanRG and @gaborbernat
<a name="release-1-18-3-fixed"></a>
Allow selecting dependencies that ship only shell completions. (2157) by AryanRG and gaborbernat
Accept absolute file:/// URLs as package specs, such as pipx install file:///wheels/tool-1-py3-none-any.whl. (#2150) by @srijan2607 and @gaborbernat
<a name="release-1-18-2-fixed"></a>
file:/// URLs as package specs, such as pipx install file:///wheels/tool-1-py3-none-any.whl. (#2150) by @srijan2607 and @gaborbernatpip or uv log, which --verbose still streams. Installer errors are still printed on failure. (#2151)pipx upgrade --verbose or pip pipx install --verbose fails, instead of repeating it after the live output. (#2153) by @gaborbernat-all command on Ctrl-C even when the interpreter drops the interrupt, which happens when the signal handler runs inside a weakref callback or a finalizer. (#2154) by @gaborbernatAccept absolute file:/// URLs as package specs, such as pipx install file:///wheels/tool-1-py3-none-any.whl. (2150) by srijan2607 and gaborbernat
In a terminal, show the pipx spinner again during installs and upgrades instead of the full pip or uv log, which --verbose still streams. Installer errors are still printed on failure. (2151)
Print the installer error once when a pipx upgrade --verbose or pip pipx install --verbose fails, instead of repeating it after the live output. (2153) by gaborbernat
Stop an -all command on Ctrl-C even when the interpreter drops the interrupt, which happens when the signal handler runs inside a weakref callback or a finalizer. (2154) by gaborbernat
Stop pip and uv when Ctrl-C lands early, instead of hanging. (#2146) by @gaborbernat
<a name="release-1-18-1-fixed"></a>
Stop pip and uv when Ctrl-C lands early, instead of hanging. (2146) by gaborbernat
Put --suffix last, except before a Windows file extension. Apps exposed by 1.17.14 keep their old name until pipx next exposes them, which renames the
<a name="release-1-18-0-added"></a>
--suffix last, except before a Windows file extension. Apps exposed by 1.17.14 keep their old name until pipx next exposes them, which renames them. (#2098) by @gaborbernatupgrade and reinstall-all refresh shared pip only after 30 days. (#2116) by @gaborbernatpipx upgrade-shared to refresh shared pip sooner. (#2116) by @gaborbernatPYTHON_LAZY_IMPORTS=normal to opt out; the entry point is pipx.__main__. (#2132) by @gaborbernatreinstall-all, upgrade-all and install-all across venvs at once. (#2137) by @gaborbernatupgrade-all; a second Ctrl-C stops them, and the next upgrade repairs what was left half-upgraded. (#2144) by @gaborbernatinstall-all --backend switches between pip and uv. (#2144) by @gaborbernat<a name="release-1-18-0-fixed"></a>
--system-site-packages is ignored by inject and upgrade-all. (#2089) by @gaborbernatrequires-python. (#2093) by @gaborbernatinterpreter upgrade move venvs off a patch-pinned standalone Python. (#2094) by @gaborbernatreinstall, install-all and --force. (#2095) by @gaborbernatinstall-all and reject bad spec files. (#2096) by @gaborbernatinstall --force --python. (#2098) by @gaborbernatpipx expose relink resources missing after a collision or a deletion. (#2099) by @gaborbernat--output json stdout and fix health JSON status. (#2101) by @gaborbernatPIPX_MAX_LOGS logs, not one extra, and rotate uv error logs too. (#2103) by @gaborbernatupgrade-all instead of crashing. (#2141) by @gaborbernat<a name="release-1-18-0-performance"></a>
pyproject.toml instead of building it twice. (#2108) by @gaborbernatsys.platform. (#2125) by @gaborbernatlist and uninstall-all. (#2138) by @gaborbernat<a name="release-1-18-0-documentation"></a>
Put --suffix last, except before a Windows file extension. Apps exposed by 1.17.14 keep their old name until pipx next exposes them, which renames them. (2098) by gaborbernat
upgrade and reinstall-all refresh shared pip only after 30 days. (2116) by gaborbernat
Run pipx upgrade-shared to refresh shared pip sooner. (2116) by gaborbernat
Set PYTHON_LAZY_IMPORTS=normal to opt out; the entry point is pipx.__main__. (2132) by gaborbernat
Defer every import, dependencies included, on Python 3.15 for faster startup. (2132) by gaborbernat
Run reinstall-all, upgrade-all and install-all across venvs at once. (2137) by gaborbernat
Let running upgrades finish on Ctrl-C in upgrade-all; a second Ctrl-C stops them, and the next upgrade repairs what was left half-upgraded. (2144) by gaborbernat
Retry uv-backend installs on a Python matching requires-python, as pip does. (2144) by gaborbernat
Translate recorded index options when install-all --backend switches between pip and uv. (2144) by gaborbernat
Warn that --system-site-packages is ignored by inject and upgrade-all. (2089) by gaborbernat
Fall back to pip with a warning when the auto-detected uv is older than 0.9.17. (2092) by gaborbernat
Use the default Python for scripts when it satisfies requires-python. (2093) by gaborbernat
Make interpreter upgrade move venvs off a patch-pinned standalone Python. (2094) by gaborbernat
Keep pins of injected packages through reinstall, install-all and --force. (2095) by gaborbernat
Restore recorded venv and pip args in install-all and reject bad spec files. (2096) by gaborbernat
Remove apps, man pages and completions an upgraded package no longer ships. (2097) by gaborbernat
Keep the interpreter on install --force --python. (2098) by gaborbernat
Make pipx expose relink resources missing after a collision or a deletion. (2099) by gaborbernat
Print only the envelope on --output json stdout and fix health JSON status. (2101) by gaborbernat
Keep users of a global pipx on their own paths and explain unwritable homes. (2102) by gaborbernat
Keep PIPX_MAX_LOGS logs, not one extra, and rotate uv error logs too. (2103) by gaborbernat
Keep the last output of a child process streamed to a terminal on macOS. (2111) by gaborbernat
Report apps whose Python is missing in upgrade-all instead of crashing. (2141) by gaborbernat
Show child output that is not valid UTF-8 instead of crashing. (2144) by gaborbernat
Mask passwords in index and package URLs in pipx's output and log files. (2144) by gaborbernat
Read a local project's name from pyproject.toml instead of building it twice. (2108) by gaborbernat
Start every pipx command 50 to 130 ms faster by importing only what it uses. (2113) by gaborbernat
Create the shared libraries 35 to 50% faster by skipping a redundant pip run. (2114) by gaborbernat
Start half as many helper processes per install by reusing what pipx knows. (2118) by gaborbernat
Skip a WMI query on Windows at startup by detecting the OS with sys.platform. (2125) by gaborbernat
Uninject orphaned dependencies in one pip call, reported on one line. (2126) by gaborbernat
Check only pipx-managed packages for updates, not every installed dependency. (2127) by gaborbernat
Start pipx commands up to 30 ms faster by loading more modules on first use. (2128) by gaborbernat
Start pipx 10 to 50 ms faster on Python 3.15 through lazy imports. (2129) by gaborbernat
Check shared pip by its files instead of starting Python on every command. (2131) by gaborbernat
Read a local wheel's package name from its metadata instead of a probe venv. (2134) by gaborbernat
Scan exposed app and man page dirs once per list and uninstall-all. (2138) by gaborbernat
Require filelock 4.2, whose lighter import speeds up most pipx commands. (2142) by gaborbernat
Correct the log directory in the platformdirs migration table. (2086)
Correct docs that described pip-only behavior or outdated defaults and paths. (2088) by gaborbernat
Match help text, troubleshooting and samples to how pipx behaves today. (2105) by gaborbernat
Build pipx wheels with Docutils 0.21.2 and later, including environments pinned to Docutils 0.22. (#2084) by @bfs2021 and @gaborbernat
<a name="release-1-17-14-fixed"></a>
<a name="release-1-17-14-documentation"></a>
--global before the subcommand instead of ignoring it. (#2082) by @Ronak-Mahidharia and @gaborbernatBuild pipx wheels with Docutils 0.21.2 and later, including environments pinned to Docutils 0.22. (2084) by bfs2021 and gaborbernat
Say that pipx rejects --global before the subcommand instead of ignoring it. (2082) by Ronak-Mahidharia and gaborbernat
Accept bare and suffixed injected package names in pipx pin --skip. (#2079) by @VedantBhayani and @gaborbernat
<a name="release-1-17-13-fixed"></a>
pipx pin --skip. (#2079) by @VedantBhayani and @gaborbernatpipx install-all rebuilds an environment unless the user passes --python. (#2081) by @feiiiiii5 and @gaborbernatAccept bare and suffixed injected package names in pipx pin --skip. (2079) by VedantBhayani and gaborbernat
Use each snapshot's recorded interpreter when pipx install-all rebuilds an environment unless the user passes --python. (2081) by feiiiiii5 and gaborbernat
Stop pipx reinstall from printing a traceback when the reinstall fails for an expected reason. (#2070) by @ParamTanna
<a name="release-1-17-12-fixed"></a>
pipx reinstall from printing a traceback when the reinstall fails for an expected reason. (#2070) by @ParamTannapipx install printing WARNING: Skipping setuptools as it is not installed. when the shared libraries are created on Python 3.12+, where setuptools is already absent. (#2071) by @officialpm and @gaborbernatpipx upgrade, pipx pin and pipx reinstall no longer append the environment suffix again, so the package keeps its name in pipx list --include-injected and stays addressable by pipx uninject. (#2072) by @feiiiiii5 and @gaborbernat<a name="release-1-17-12-documentation"></a>
Stop pipx reinstall from printing a traceback when the reinstall fails for an expected reason. (2070) by ParamTanna
Stop pipx install printing WARNING: Skipping setuptools as it is not installed. when the shared libraries are created on Python 3.12+, where setuptools is already absent. (2071) by officialpm and gaborbernat
Stop an injected package in a suffixed environment from being renamed every time its record is rewritten: pipx upgrade, pipx pin and pipx reinstall no longer append the environment suffix again, so the package keeps its name in pipx list --include-injected and stays addressable by pipx uninject. (2072) by feiiiiii5 and gaborbernat
Update the pipx logo author credit. (2073)
Hide the extra documentation TOC toggle on narrow screens.
<a name="release-1-17-11-documentation"></a>
Hide the extra documentation TOC toggle on narrow screens. (2064)
Remove an environment that has no pipx metadata and an interpreter that no longer runs, instead of crashing pipx uninstall and pipx uninstall-all. (#2
<a name="release-1-17-10-fixed"></a>
pipx uninstall and pipx uninstall-all. (#2059) by @hemcharan710-afk and @gaborbernat#. A script installed by an earlier release under its directory's name no longer upgrades; uninstall it and install it again. (#2060)pipx install bare.py), contains [, or starts with a quoted ~, and stop the upgrade hint from suggesting a PyPI reinstall for a script. (#2062) by @gaborbernatRemove an environment that has no pipx metadata and an interpreter that no longer runs, instead of crashing pipx uninstall and pipx uninstall-all. (2059) by hemcharan710-afk and gaborbernat
Derive local script command names from the filename when parent directories contain #. A script installed by an earlier release under its directory's name no longer upgrades; uninstall it and install it again. (2060)
Install a local PEP 723 script from its file when the path reads as a PyPI name (pipx install bare.py), contains [, or starts with a quoted ~, and stop the upgrade hint from suggesting a PyPI reinstall for a script. (2062) by gaborbernat
Stop adding \ -E\ to an app script's shebang when the longer line would exceed the kernel's limit, which made the script fail on macOS with Exec forma
<a name="release-1-17-9-fixed"></a>
Exec format error. (#2058) by @feiiiiii5, @OpenCode and @gaborbernatStop adding ` -E` to an app script's shebang when the longer line would exceed the kernel's limit, which made the script fail on macOS with Exec format error. (2058) by feiiiiii5, OpenCode and gaborbernat
Remove leftover shell completion scripts when running pipx uninject.
<a name="release-1-17-8-fixed"></a>
pipx uninject. (#2055)Remove leftover shell completion scripts when running pipx uninject . ( #2055 )
Remove leftover shell completion scripts when running pipx uninject. (2055)
Prevent pipx run from sharing cached environments across different requirement lists or argument boundaries. This changes cache keys; run pipx cache p
<a name="release-1-17-7-fixed"></a>
pipx run from sharing cached environments across different requirement lists or argument boundaries. This changes cache keys; run pipx cache purge to remove old entries. (#2053) by @januththedev and @gaborbernatPrevent pipx run from sharing cached environments across different requirement lists or argument boundaries. This changes cache keys; run pipx cache purge to remove old entries. (2053) by januththedev and gaborbernat
Record each tool's dependency group as its lock's default so pipx manifest sync installs what pipx manifest lock wrote. Run pipx manifest lock again t
<a name="release-1-17-6-fixed"></a>
pipx manifest sync installs what pipx manifest lock wrote. Run pipx manifest lock again to fix existing locks. (#2049)<a name="release-1-17-6-documentation"></a>
Record each tool's dependency group as its lock's default so pipx manifest sync installs what pipx manifest lock wrote. Run pipx manifest lock again to fix existing locks. (2049)
Fix the argument order in the combined inject command example. (2044) by agammann
Use direct URL requirements for the Git install example with extras. (2045)
Report failed environments when running pipx reinstall-all.
<a name="release-1-17-5-fixed"></a>
pipx reinstall-all. (#2042)Report failed environments when running pipx reinstall-all . ( #2042 )
Report failed environments when running pipx reinstall-all. (2042)
pipx upgrade of a package installed from a local path, wheel, or VCS URL no longer reports "already at latest version". It now says the package is unc
<a name="release-1-17-4-fixed"></a>
pipx upgrade of a package installed from a local path, wheel, or VCS URL no longer reports "already at latest version". It now says the package is unchanged because it is installed from a local source and that no package index was checked, and suggests reinstalling by package name to track index releases. (#2040)pipx upgrade of a package installed from a local path, wheel, or VCS URL no longer reports "already at latest version". It now says the package is unchanged because it is installed from a local source and that no package index was checked, and suggests reinstalling by package name to track index releases. (2040)
Report a clear error when PIPX_MAX_LOGS is not a non-negative integer, instead of crashing on every pipx command. Empty or whitespace-only values fall
<a name="release-1-17-3-fixed"></a>
--pip-args the way a shell would, so a quoted path with spaces such as --find-links '/tmp/foo bar' reaches pip intact instead of failing to parse. On Windows pipx now drops the quotes around each argument and keeps backslashes as path separators. (#2033) by @r3wretrhypipx runpip from printing uv DEBUG logs on the uv backend. (#2035) by @anandghegde<a name="release-1-17-3-documentation"></a>
--pip-args flag the uv backend translates instead of only four. (#2037) by @hxperl and @claudeReport a clear error when PIPX_MAX_LOGS is not a non-negative integer, instead of crashing on every pipx command. Empty or whitespace-only values fall back to the default everywhere, including log setup. (2029) by hktitof
Split --pip-args the way a shell would, so a quoted path with spaces such as --find-links '/tmp/foo bar' reaches pip intact instead of failing to parse. On Windows pipx now drops the quotes around each argument and keeps backslashes as path separators. (2033) by r3wretrhy
Stop pipx runpip from printing uv DEBUG logs on the uv backend. (2035) by anandghegde
List every --pip-args flag the uv backend translates instead of only four. (2037) by hxperl and claude
Fix KeyError stderr noise when installing packages in Python3.15. (#2026) by @Cycloctane
<a name="release-1-17-2-fixed"></a>
KeyError stderr noise when installing packages in Python3.15. (#2026) by @CycloctaneFix KeyError stderr noise when installing packages in Python3.15. (2026) by Cycloctane
pipx environment now reports PIPX_MAX_LOGS, and pipx environment --value PIPX_MAX_LOGS no longer exits with invalid choice. (#2024) by @dylanpulver an
<a name="release-1-17-1-fixed"></a>
pipx environment now reports PIPX_MAX_LOGS, and pipx environment --value PIPX_MAX_LOGS no longer exits with invalid choice. (#2024) by @dylanpulver and @gaborbernatpipx environment now reports PIPX_MAX_LOGS, and pipx environment --value PIPX_MAX_LOGS no longer exits with invalid choice. (2024) by dylanpulver and gaborbernat
Fix pipx not being able to discover packages in separated platlib directories. (#1999) by @Cycloctane and @gaborbernat
<a name="release-1-16-7-fixed"></a>
<a name="release-1-16-7-documentation"></a>
PIPX_HOME, which resolves to %LOCALAPPDATA%\pipx\pipx rather than %LOCALAPPDATA%\pipx. (#2002) by @aroh3006Fix pipx not being able to discover packages in separated platlib directories. (1999) by Cycloctane and gaborbernat
Retry transient failures when fetching the python-build-standalone release index and downloading interpreter archives, resuming an interrupted archive download from the bytes already received instead of starting over. (2001) by gaborbernat
Correct the documented Windows default for PIPX_HOME, which resolves to %LOCALAPPDATA%pipxpipx rather than %LOCALAPPDATA%pipx. (2002) by aroh3006
Stop appending a second .exe on Windows to the app name pipx run infers.
<a name="release-1-16-6-fixed"></a>
.exe on Windows to the app name pipx run infers. (#1189)pipx run infers the app name from a VCS URL, a local path, or a name it normalized, instead of passing a guess to uv tool run. Reusing that venv no longer reinstalls the package on every run. (#1994)Stop appending a second .exe on Windows to the app name pipx run infers. (1189)
Run the console script a package declares when pipx run infers the app name from a VCS URL, a local path, or a name it normalized, instead of passing a guess to uv tool run. Reusing that venv no longer reinstalls the package on every run. (1994)
Honor the version specifier when pipx upgrade --install installs a missing package.
<a name="release-1-16-5-fixed"></a>
pipx upgrade --install installs a missing package. (#1987)Honor the version specifier when pipx upgrade --install installs a missing package. (1987)
Bundle colorama and tomli in the zipapp so the single pipx.pyz works on Windows and on Python 3.10. (#1978, #1984)
<a name="release-1-16-4-fixed"></a>
colorama and tomli in the zipapp so the single pipx.pyz works on Windows and on Python 3.10. (#1978, #1984)PIPX_MAX_LOGS=0 now prunes the log files instead of keeping all of them. (#1988) by @marko1olo<a name="release-1-16-4-documentation"></a>
Bundle colorama and tomli in the zipapp so the single pipx.pyz works on Windows and on Python 3.10. (1978, 1984)
Fix the Release Notes link published in package metadata. (1980)
PIPX_MAX_LOGS=0 now prunes the log files instead of keeping all of them. (1988) by marko1olo
Fix the documentation links that 404 after the Sphinx move, including the PyPI Release Notes link. (1980)
Allow read-only global list commands when venv lock files are inaccessible.
<a name="release-1-16-3-fixed"></a>
<a name="release-1-16-3-documentation"></a>
Allow read-only global list commands when venv lock files are inaccessible. (1974)
Direct Linux users to PEP 668-compatible installation methods. (1976)
Stop venv inspection from crashing on Python 3.15 when a dist-info directory has no Name metadata field. importlib.metadata now raises KeyError for mi
<a name="release-1-16-2-fixed"></a>
dist-info directory has no Name metadata field. importlib.metadata now raises KeyError for missing metadata keys instead of returning None; such distributions are skipped again, as on earlier Python versions. (#1971) by @gaborbernatStop venv inspection from crashing on Python 3.15 when a dist-info directory has no Name metadata field. importlib.metadata now raises KeyError for missing metadata keys instead of returning None; such distributions are skipped again, as on earlier Python versions. (1971) by gaborbernat
Stop install and list from crashing when the pipx bin directory contains an executable pipx did not create. Scanning for launcher ownership decoded ar
<a name="release-1-16-1-fixed"></a>
install and list from crashing when the pipx bin directory contains an executable pipx did not create. Scanning for launcher ownership decoded arbitrary binary content as an interpreter path, which raised UnicodeDecodeError on Windows, or ValueError for a path holding a NUL byte. Such a file is now treated as not owned by the venv. (#1965)Stop install and list from crashing when the pipx bin directory contains an executable pipx did not create. Scanning for launcher ownership decoded arbitrary binary content as an interpreter path, which raised UnicodeDecodeError on Windows, or ValueError for a path holding a NUL byte. Such a file is now treated as not owned by the venv. (1965)
Add pipx list --outdated and JSON output.
<a name="release-1-16-0-added"></a>
pipx list --outdated and JSON output. (#149)requires-python a package declares. When the default interpreter fails it, pipx looks for one on the system that satisfies it and builds the environment there, so pipx install mytool no longer needs the user to work out the right --python. Pass --fetch-python=missing to let pipx download a matching interpreter when the system carries none, and name --python yourself to keep the last word. (#387)pipx run package names. (#618)pipx list to select installed packages by name. (#640)--output to structured commands. (#828)pipx_result_version 1. Every --output json document now carries the command as a list of CLI tokens, a status of success, partial, or error, the process exit_code, the command data, and a top-level errors list whose entries each have a stable code and message alongside the environment and package they concern. A failure that stops a command before it builds a result renders the same envelope. (#828)pipx reinstall and pipx reinstall-all the structured output the other commands carry. They printed straight to the terminal, so --quiet left uninstalled NAME! behind and no --output json existed to read the result from a script. Both now report through the shared renderer. (#828)pipx cache, pipx interpreter, pipx upgrade-shared, pipx manifest lock and pipx manifest sync the structured output the other commands carry, so --quiet silences them and --output json hands a script the result. The cache and interpreter subcommands take --quiet and --verbose for the first time, since the shared options had passed them by. pipx ensurepath goes on printing its guidance, because its job is to tell a person what to add to a shell profile. (#828)--output json to pipx inject and pipx uninject. (#828)pip and uv during a plain pipx install, in place of the pipx spinner. pipx hands the installer a pseudo-terminal, which is the only way uv reports progress, and asks uv for its default output rather than the quiet one. A redirected stream keeps the previous behaviour. (#1069)inject and --preinstall. (#1411)pipx install --upgrade to reconcile apps with package specs. (#1572)share/bash-completion/completions, share/zsh/site-functions or share/fish/vendor_completions.d gets those files linked under PIPX_COMPLETION_DIR, which defaults to ~/.local/share. bash and fish read those locations on their own; zsh needs the site-functions directory on its fpath. Uninstalling the package takes the links away. (#1604)pipx reset, which uninstalls every pipx-managed package and removes the shared libraries, the caches, the standalone interpreters, the logs and the trash, so pipx starts over from a fresh install. It asks before it removes anything, --yes answers for a script, and --dry-run lists what would go. (#1606)pipx run. (#1613)pipx cache and pipx run --refresh. (#1681)--include-apps-from for selected dependencies. (#1725)pipx exec ENVIRONMENT APPLICATION for installed environments. (#1726)PIPX_HOME to the platform data directory on macOS and Windows again, which restores ~/Library/Application Support/pipx on macOS. platformdirs reads XDG_DATA_HOME and XDG_CACHE_HOME on macOS, so exporting those moves the pipx directories. A pipx home from an earlier release keeps working as a fallback. (#1946)pipx manifest: use pipx manifest lock and pipx manifest sync in place of the top-level pipx lock and pipx sync. Keeping both verbs under one noun matches pipx cache and pipx interpreter and leaves the top-level command list about the manifest rather than two loose verbs.--json only on pipx list, where it prints the versioned package snapshot that install-all reads back. Every other command dropped the --json alias in favour of --output json, so the snapshot format and the result envelope no longer share a flag.ENVIRONMENT across inject, uninject, expose, unexpose, pin, unpin, uninstall, reinstall, and exec, and fix the uninject help, which described the argument as the environment to inject into rather than uninject from.install, upgrade, and upgrade-all results, list PIPX_GLOBAL_COMPLETION_DIR in pipx environment, and show the shell-completion directory in pipx list. Completions had a global override that pipx honoured but never surfaced, and the records omitted which Python and backend produced a venv.--include-apps-from to --include-resources-from and the manifest key to match. The option always exposed manual pages and shell completions alongside apps, so the new name describes what it does; --include-apps keeps its name. A venv recorded under the old key is migrated on read.<a name="release-1-16-0-fixed"></a>
requires-python. pipx matched only on the minor version, so it rejected an installed 3.13.7 for >=3.13.5 and accepted 3.14.6 for <3.14.1. It now queries each resolved interpreter and keeps the first whose full version satisfies the constraint. (#387)pipx list on systems that copy launchers. (#997)pip, so pip held its bar back and printed a finished one once the download had ended. (#1069)PIPX_HOME when creating environments. (#1327)pipx run. (#1423)ensurepath --global update the system PATH configuration instead of root's shell profiles. (#1452)pipx_metadata.json after pipx runpip ... install replaces the main package, so future upgrade and reinstall commands stop following a stale editable source path. (#1473)git+file:///path/to/repository@revision. (#1583)--find-links paths before pipx changes the working directory. (#1637)pipx run --with being silently dropped for PEP 723 scripts on the pip backend; the extra packages are now installed into the temporary venv. (#1850)pipx uninject leaving the injected package's man page symlinks behind. (#1853)--editable when installing a local package after a non-local package. (#1856)pipx environment --value choices. (#1856)pipx unpin. (#1856)-c and -f pip arguments before invoking pip. (#1856)--no-deps before invoking uv. (#1856)install --force from saving its internal --force-reinstall option in package metadata. (#1856)pipx upgrade --include-injected. (#1856)pipx run environments. (#1856)PIPX_HOME still keeps both inside it. (#1946)5xx or rate-limit response no longer fails the install. (#1960) by @gaborbernatpipx manifest lock as all-or-nothing. When a manifest declares locks for several tools, pipx wrote the regenerated files one at a time, so a failure partway left some locks new and others old. Each target is now backed up before it is replaced and every applied lock is rolled back if any replacement fails.pipx run or pipx install script, so a stalled or oversized URL can no longer hang pipx or exhaust memory. pipx run also accepts a script URL with a query string, such as tool.py?raw=1, by matching on the URL path.requires-python on the pip-backed pipx run. Without an explicit --python, pipx now picks an interpreter that satisfies the constraint, matching what the uv backend already does; with an explicit --python that fails the constraint it reports a clear error instead of running on an unsupported interpreter. A malformed inline metadata block now produces a readable message rather than a traceback.pipx run --with packages in the run-cache key. Because they were absent, pipx run TOOL and pipx run --with EXTRA TOOL shared one cached environment, so extras injected by one invocation leaked into later runs that asked for none. Each distinct set of extras now gets its own environment, and the extras are injected only when that environment is first built.install --force and reinstall take while replacing an environment in pipx's trash rather than beside the live environments. A backup placed in the venvs directory was picked up as a broken environment by a concurrent list or reinstall-all; the trash shares the home's filesystem, so restoring a backup is still an atomic rename.pipx run non-blocking. pipx used to wait for a lock on every other cached environment, so a concurrent pipx run whose install held one of those locks stalled the new run, a stall that lasted the whole install on Windows. The sweep now skips any environment another run is holding.uv found on PATH before using it, and bound every uv --version call with a timeout. A broken or hanging uv on PATH previously slipped past discovery and stalled the next command; pipx now skips such a binary and reports a clear error instead of hanging.--suffix that contains anything but letters, digits, and the characters . _ - + @. A suffix is spliced straight into the names of the links pipx writes into PIPX_BIN_DIR and PIPX_MAN_DIR, so a value such as /../../owned could previously place those links outside pipx's own directories.pipx expose as a partial or failed operation when a resource cannot be linked because a foreign file already occupies its target name. The command previously claimed success while silently leaving those apps or manual pages unexposed; it now lists each conflict in the structured result and exits non-zero.UV_NO_PROGRESS=1 on every uv call. The override silenced uv's progress bar even when pipx asked to draw one, and it ignored a UV_NO_PROGRESS already set in the environment. pipx now suppresses the bar only in quiet, JSON, and non-interactive runs, and defers to the caller's UV_NO_PROGRESS when it does want progress shown.<a name="release-1-16-0-performance"></a>
pipx environment --value entry. (#1856)pipx run PATH lookup when warning about an existing app. (#1856)<a name="release-1-16-0-documentation"></a>
<a name="release-1-16-0-removed"></a>
PIPX_HOME_ALLOW_SPACE environment variable and the warning about spaces in the pipx home path. pip and uv both write a /bin/sh wrapper as the shebang when the interpreter path contains a space, so applications installed into such a path run. (#1946)Add pipx list –outdated and JSON output. ( #149 )
Honour the requires-python a package declares. When the default interpreter fails it, pipx looks for one on the system that satisfies it and builds the environment there, so pipx install mytool no longer needs the user to work out the right –python . Pass –fetch-python=missing to let pipx download a matching interpreter when the system carries none, and name –python yourself to keep the last word. ( #387 )
Normalize inferred pipx run package names. ( #618 )
Allow pipx list to select installed packages by name. ( #640 )
Add –output to structured commands. ( #828 )
Freeze the structured result envelope at pipx_result_version 1. Every –output json document now carries the command as a list of CLI tokens, a status of success , partial , or error , the process exit_code , the command data , and a top-level errors list whose entries each have a stable code and message alongside the environment and package they concern. A failure that stops a command before it builds a result renders the same envelope. ( #828 )
Add quiet and JSON output for package maintenance. ( #828 )
Give pipx reinstall and pipx reinstall-all the structured output the other commands carry. They printed straight to the terminal, so –quiet left uninstalled NAME! behind and no –output json existed to read the result from a script. Both now report through the shared renderer. ( #828 )
Give pipx cache , pipx interpreter , pipx upgrade-shared , pipx manifest lock and pipx manifest sync the structured output the other commands carry, so –quiet silences them and –output json hands a script the result. The cache and interpreter subcommands take –quiet and –verbose for the first time, since the shared options had passed them by. pipx ensurepath goes on printing its guidance, because its job is to tell a person what to add to a shell profile. ( #828 )
Add –output json to pipx inject and pipx uninject . ( #828 )
Infer the app name when running packages from VCS URLs. ( #854 )
Stream installer output during verbose installs. ( #1069 )
Draw the download progress bar of pip and uv during a plain pipx install , in place of the pipx spinner. pipx hands the installer a pseudo-terminal, which is the only way uv reports progress, and asks uv for its default output rather than the quiet one. A redirected stream keeps the previous behaviour. ( #1069 )
Allow commands to skip shared-library maintenance. ( #1278 )
Install PEP 723 scripts as persistent applications. ( #1388 )
Point library install errors to inject and –preinstall . ( #1411 )
Add commands to diagnose and repair broken environment interpreters. ( #1442 )
Add explicit tool manifests with separate PEP 751 locks. ( #1506 )
Add pipx install –upgrade to reconcile apps with package specs. ( #1572 )
Expose the shell completion scripts a package ships, the way pipx already exposes its man pages. A wheel that installs into share/bash-completion/completions , share/zsh/site-functions or share/fish/vendor_completions.d gets those files linked under PIPX_COMPLETION_DIR , which defaults to ~/.local/share . bash and fish read those locations on their own; zsh needs the site-functions directory on its fpath . Uninstalling the package takes the links away. ( #1604 )
Add pipx reset , which uninstalls every pipx-managed package and removes the shared libraries, the caches, the standalone interpreters, the logs and the trash, so pipx starts over from a fresh install. It asks before it removes anything, –yes answers for a script, and –dry-run lists what would go. ( #1606 )
Add Python interpreter arguments to pipx run . ( #1613 )
Add commands to hide and restore resources exposed from an environment. ( #1645 )
Install the generated pipx manual page from wheels. ( #1657 )
Add pipx cache and pipx run –refresh . ( #1681 )
Add –include-apps-from for selected dependencies. ( #1725 )
Add pipx exec ENVIRONMENT APPLICATION for installed environments. ( #1726 )
Support injecting extras into a main package. ( #1805 )
Install from PEP 751 lock files. ( #1807 )
Add dependency cooldowns. ( #1811 )
Validate requested apps and restore prior environments on failure. ( #1908 )
Default PIPX_HOME to the platform data directory on macOS and Windows again, which restores ~/Library/Application Support/pipx on macOS. platformdirs reads XDG_DATA_HOME and XDG_CACHE_HOME on macOS, so exporting those moves the pipx directories. A pipx home from an earlier release keeps working as a fallback. ( #1946 )
Group the manifest commands under pipx manifest : use pipx manifest lock and pipx manifest sync in place of the top-level pipx lock and pipx sync . Keeping both verbs under one noun matches pipx cache and pipx interpreter and leaves the top-level command list about the manifest rather than two loose verbs.
Keep –json only on pipx list , where it prints the versioned package snapshot that install-all reads back. Every other command dropped the –json alias in favour of –output json , so the snapshot format and the result envelope no longer share a flag.
Name the existing-environment argument ENVIRONMENT across inject , uninject , expose , unexpose , pin , unpin , uninstall , reinstall , and exec , and fix the uninject help, which described the argument as the environment to inject into rather than uninject from.
Record the interpreter and backend in the structured install , upgrade , and upgrade-all results, list PIPX_GLOBAL_COMPLETION_DIR in pipx environment , and show the shell-completion directory in pipx list . Completions had a global override that pipx honoured but never surfaced, and the records omitted which Python and backend produced a venv.
Rename –include-apps-from to –include-resources-from and the manifest key to match. The option always exposed manual pages and shell completions alongside apps, so the new name describes what it does; –include-apps keeps its name. A venv recorded under the old key is migrated on read.
Support standalone Python downloads on Windows ARM64. ( #1856 )
Check a candidate interpreter’s real patch version against requires-python . pipx matched only on the minor version, so it rejected an installed 3.13.7 for >=3.13.5 and accepted 3.14.6 for <3.14.1 . It now queries each resolved interpreter and keeps the first whose full version satisfies the constraint. ( #387 )
Keep existing exposed files when copy-based environments provide the same resource name. ( #540 )
Recover custom paths when pipx manages its own installation on Unix. ( #774 )
Keep install failures in JSON with the correct environment. ( #828 )
Show injected apps in pipx list on systems that copy launchers. ( #997 )
Serialize shared-library maintenance across pipx processes. ( #1056 )
Wait for an installation before listing its environment. ( #1056 )
Draw the installer progress bar while the download runs. pipx reads the installer output over a pipe, which hid the terminal from pip , so pip held its bar back and printed a finished one once the download had ended. ( #1069 )
Preserve symlinks in PIPX_HOME when creating environments. ( #1327 )
Create Windows launchers for PEP 723 scripts. ( #1388 )
Preserve the terminal encoding for applications started by pipx run . ( #1423 )
Make ensurepath –global update the system PATH configuration instead of root’s shell profiles. ( #1452 )
Refresh pipx_metadata.json after pipx runpip … install replaces the main package, so future upgrade and reinstall commands stop following a stale editable source path. ( #1473 )
Accept bare local Git and Mercurial URLs such as git+file:///path/to/repository@revision . ( #1583 )
Recreate the shared environment when pip cannot run. ( #1606 )
Resolve local –find-links paths before pipx changes the working directory. ( #1637 )
Keep pipx startup usable when locked files prevent trash cleanup. ( #1847 )
Fix pipx run –with being silently dropped for PEP 723 scripts on the pip backend; the extra packages are now installed into the temporary venv. ( #1850 )
Fix pipx uninject leaving the injected package’s man page symlinks behind. ( #1853 )
Preserve –editable when installing a local package after a non-local package. ( #1856 )
Emit path warnings after logging setup for the active local or global context. ( #1856 )
Treat empty values for pipx path environment variables as unset. ( #1856 )
Apply a 30-second timeout to standalone Python index and archive network requests. ( #1856 )
Enforce pip’s minimum supported version when shared-library upgrades include a user pin. ( #1856 )
Remove exposed apps that use a venv suffix when uninjecting packages. ( #1856 )
Report corrupt venv metadata as missing without aborting list and bulk commands. ( #1856 )
Return user-set values for the advertised pipx environment –value choices. ( #1856 )
Keep existing venv metadata when pipx cannot write its replacement. ( #1856 )
Keep trash cleanup non-fatal during directory races and failed moves. ( #1856 )
List only packages whose pin state changed during pipx unpin . ( #1856 )
Reject both Windows path separators in package names. ( #1856 )
Resolve relative paths in attached -c and -f pip arguments before invoking pip. ( #1856 )
Avoid import crashes when stderr or its encoding is unavailable. ( #1856 )
Keep Windows uninject working while an exposed app runs. ( #1856 )
Translate pip binary and trusted-host options to valid uv run arguments, and reject –no-deps before invoking uv. ( #1856 )
Validate members before extracting a standalone Python archive on Python 3.10.0-3.10.11, which predate tarfile’s data filter. pipx now refuses any entry whose path or link target would escape the download directory instead of falling back to an unfiltered extraction. ( #1856 )
Return a resolution error when standalone Python lacks a build for the current platform. ( #1856 )
Prevent install –force from saving its internal –force-reinstall option in package metadata. ( #1856 )
Continue bulk interpreter upgrades after finding a corrupt standalone interpreter. ( #1856 )
Skip shared-library maintenance for no-op installs. ( #1856 )
Compare metadata versions by parsed release components when selecting shared libraries. ( #1856 )
Wait for the animation thread to stop before clearing its final frame. ( #1856 )
Preserve standalone archive extraction on Python 3.10 releases without the tar filter API. ( #1856 )
Preserve noncanonical package prefixes when completing names of installed virtual environments. ( #1856 )
Preserve stored pip arguments for injected packages during pipx upgrade –include-injected . ( #1856 )
Preserve caller-owned pip arguments when creating the shared-library environment. ( #1856 )
Use tar’s data filter when extracting standalone Python archives for consistent safety. ( #1856 )
Skip cache tag files when removing expired pipx run environments. ( #1856 )
Allow forced installs in existing uv environments. ( #1924 )
Store the venv cache and the logs in the platform cache and log directories on every platform, and keep them out of a pipx home that only exists for backwards compatibility. Setting PIPX_HOME still keeps both inside it. ( #1946 )
Retry fetching a standalone Python build when GitHub’s release CDN returns a transient error, so a momentary 5xx or rate-limit response no longer fails the install. ( #1960 ) by @gaborbernat
Apply pipx manifest lock as all-or-nothing. When a manifest declares locks for several tools, pipx wrote the regenerated files one at a time, so a failure partway left some locks new and others old. Each target is now backed up before it is replaced and every applied lock is rolled back if any replacement fails.
Apply a 30-second timeout and a 10 MiB size limit when downloading a remote pipx run or pipx install script, so a stalled or oversized URL can no longer hang pipx or exhaust memory. pipx run also accepts a script URL with a query string, such as tool.py?raw=1 , by matching on the URL path.
Honour a script’s PEP 723 requires-python on the pip-backed pipx run . Without an explicit –python , pipx now picks an interpreter that satisfies the constraint, matching what the uv backend already does; with an explicit –python that fails the constraint it reports a clear error instead of running on an unsupported interpreter. A malformed inline metadata block now produces a readable message rather than a traceback.
Include pipx run –with packages in the run-cache key. Because they were absent, pipx run TOOL and pipx run –with EXTRA TOOL shared one cached environment, so extras injected by one invocation leaked into later runs that asked for none. Each distinct set of extras now gets its own environment, and the extras are injected only when that environment is first built.
Keep the backups that install –force and reinstall take while replacing an environment in pipx’s trash rather than beside the live environments. A backup placed in the venvs directory was picked up as a broken environment by a concurrent list or reinstall-all ; the trash shares the home’s filesystem, so restoring a backup is still an atomic rename.
Make a standalone Python upgrade atomic. pipx used to delete the existing interpreter before downloading its replacement, so a failed download or unpack left no interpreter at all. The new build is now staged beside the old one and swapped in only once it is complete, and a failed swap restores the previous build.
Make the expired-cache sweep that runs before pipx run non-blocking. pipx used to wait for a lock on every other cached environment, so a concurrent pipx run whose install held one of those locks stalled the new run, a stall that lasted the whole install on Windows. The sweep now skips any environment another run is holding.
Probe a uv found on PATH before using it, and bound every uv –version call with a timeout. A broken or hanging uv on PATH previously slipped past discovery and stalled the next command; pipx now skips such a binary and reports a clear error instead of hanging.
Reject a –suffix that contains anything but letters, digits, and the characters . _ - + @ . A suffix is spliced straight into the names of the links pipx writes into PIPX_BIN_DIR and PIPX_MAN_DIR , so a value such as /../../owned could previously place those links outside pipx’s own directories.
Remove a dropped app or man page during upgrade only when pipx still owns the exposed file, so a command a user or another package replaced is left in place.
Report pipx expose as a partial or failed operation when a resource cannot be linked because a foreign file already occupies its target name. The command previously claimed success while silently leaving those apps or manual pages unexposed; it now lists each conflict in the structured result and exits non-zero.
Stop forcing UV_NO_PROGRESS=1 on every uv call. The override silenced uv’s progress bar even when pipx asked to draw one, and it ignored a UV_NO_PROGRESS already set in the environment. pipx now suppresses the bar only in quiet, JSON, and non-interactive runs, and defers to the caller’s UV_NO_PROGRESS when it does want progress shown.
Track exposed shell completions through the full environment lifecycle. Stale-resource cleanup during install, upgrade, and reinstall, the repair relink check, and the ownership filter now include completions alongside apps and manual pages, so a completion a package stops shipping is removed instead of lingering.
Check upgrades in parallel and skip installs for current packages. ( #1353 )
Index installed distributions during environment inspection. ( #1856 )
Cache each managed environment’s site-packages path. ( #1856 )
Read environment metadata once per interpreter upgrade. ( #1856 )
Cache shared-library validity checks within each pipx process. ( #1856 )
List managed environments only when shell completion requests them. ( #1856 )
Cache resolved pipx context paths. ( #1856 )
Compute only the requested pipx environment –value entry. ( #1856 )
Reuse the pipx run PATH lookup when warning about an existing app. ( #1856 )
Resolve the default Python interpreter on first use instead of import. ( #1856 )
Inspect legacy environments once during uninstall and reinstall. ( #1856 )
Document the pipx application scope and feature boundaries. ( #177 )
Remove the PIPX_HOME_ALLOW_SPACE environment variable and the warning about spaces in the pipx home path. pip and uv both write a /bin/sh wrapper as the shebang when the interpreter path contains a space, so applications installed into such a path run. ( #1946 )
🐍 PyPI release 📜 Full Changelog
Retry fetching a standalone Python build when GitHub's release CDN returns a transient error, so a momentary 5xx or rate-limit response no longer fail
<a name="release-1-15-1-fixed"></a>
5xx or rate-limit response no longer fails the install. (#1960) by @gaborbernatRetry fetching a standalone Python build when GitHub's release CDN returns a transient error, so a momentary 5xx or rate-limit response no longer fails the install. (1960) by gaborbernat
Add a --dry-run flag to pipx ensurepath that reports which directories would be added to PATH without modifying PATH or any shell configuration file.
<a name="release-1-15-0-added"></a>
--dry-run flag to pipx ensurepath that reports which directories would be added to PATH without modifying PATH or any shell configuration file. (#1014)<a name="release-1-15-0-fixed"></a>
pipx uninject for uv-backed environments, where uv lacks pip's list --not-required option. Both backends now derive the not-required set from installed distribution metadata, so they behave identically, and a dependency pulled in only by another package's extra is kept instead of being treated as removable. (#1841)Add a --dry-run flag to pipx ensurepath that reports which directories would be added to PATH without modifying PATH or any shell configuration file. (1014)
Fix pipx uninject for uv-backed environments, where uv lacks pip's list --not-required option. Both backends now derive the not-required set from installed distribution metadata, so they behave identically, and a dependency pulled in only by another package's extra is kept instead of being treated as removable. (1841)
Restore the original package if pipx reinstall-all is interrupted during reinstall.
<a name="release-1-14-1-fixed"></a>
pipx reinstall-all is interrupted during reinstall. (#966)pipx.util before pipx.paths. (#1333)pipx inject --force reinstalls injected packages without persisting the force-reinstall option in package metadata. (#1545)pipx pin <app> --injected-only so it can pin injected packages when the main app is already pinned. (#1835) by @marko1oloRestore the original package if pipx reinstall-all is interrupted during reinstall. (966)
Allow importing pipx.util before pipx.paths. (1333)
Ensure pipx inject --force reinstalls injected packages without persisting the force-reinstall option in package metadata. (1545)
Preserve installer errors when package-name detection fails during local package installs. (1567)
Expose manual pages for editable local package installs. (1793)
Fixed pipx pin <app> --injected-only so it can pin injected packages when the main app is already pinned. (1835) by marko1olo
Add --no-path-check to pipx run to skip the warning when the app is already on PATH. Useful for shim scripts that wrap pipx run under the same name as
<a name="release-1-14-0-added"></a>
--no-path-check to pipx run to skip the warning when the app is already on PATH. Useful for shim scripts that wrap pipx run <app> under the same name as the app. (#1824)<a name="release-1-14-0-documentation"></a>
Add --no-path-check to pipx run to skip the warning when the app is already on PATH. Useful for shim scripts that wrap pipx run <app> under the same name as the app. (1824)
Use the bootstrap pipx executable when adding PATH in self-managed installs. (1481)
Update the error message in get-pipx.py; it is obsoleted, not deprecated. (#1813) by @Spitfire1900
<a name="release-1-13-0-added"></a>
PIPX_DISABLE_SHARED_LIBS_AUTO_UPGRADE to skip automatic shared library upgrades. (#1650)<a name="release-1-13-0-fixed"></a>
PYTHONPATH. (#1584)--fetch-missing-python. (#1774)<a name="release-1-13-0-documentation"></a>
runpip. (#1802)Add PIPX_DISABLE_SHARED_LIBS_AUTO_UPGRADE to skip automatic shared library upgrades. (1650)
Update the error message in get-pipx.py; it is obsoleted, not deprecated. (1813) by Spitfire1900
Install app scripts with shebangs that ignore PYTHONPATH. (1584)
Refresh cached standalone Python indexes written by older pipx versions before using --fetch-missing-python. (1774)
Document how to clear cache warnings from runpip. (1802)
Deprecate --fetch-missing-python and PIPX_FETCH_MISSING_PYTHON; both are now aliases for --fetch-python=missing / PIPX_FETCH_PYTHON=missing. PIPX_FETC…
<a name="release-1-12-0-added"></a>
--fetch-python and PIPX_FETCH_PYTHON to control standalone Python downloads, with values always, missing, or never. (#1663) by @13steinj and @gaborbernatuv backend. Install pipx[uv] (or put uv on PATH) and pipx will create venvs with uv venv, manage packages with uv pip, and run ephemeral apps via uv tool run. Default change: when uv is reachable, pipx uses it for new venvs by default. Existing venvs keep their recorded backend; flipping a venv requires pipx reinstall NAME --backend X. Set PIPX_DEFAULT_BACKEND=pip to force pip even when uv is available, or pass --backend pip per command. pipx install pip always picks the pip backend (uv venvs have no pip). Selection precedence: --backend > recorded venv metadata > PIPX_DEFAULT_BACKEND > auto-detect. The env var sits below metadata so setting PIPX_DEFAULT_BACKEND=uv does not silently retarget existing pip-backed venvs; the recorded backend wins until you flip it explicitly. pipx environment exposes the resolved backend and its source as PIPX_RESOLVED_BACKEND and PIPX_BACKEND_SOURCE. Metadata version bump: the venv metadata file format moves from 0.5 to 0.6 to record the chosen backend. Running this pipx version against an existing venv rewrites its metadata to 0.6 on the next install/upgrade. If you downgrade pipx after that, the older version raises Unknown metadata version 0.6 and you'll need to reinstall the affected venvs from the older pipx (pipx reinstall NAME). (#1808)<a name="release-1-12-0-deprecated"></a>
--fetch-missing-python and PIPX_FETCH_MISSING_PYTHON; both are now aliases for --fetch-python=missing / PIPX_FETCH_PYTHON=missing. PIPX_FETCH_MISSING_PYTHON=0 (and other falsy values) now disables fetching, where previously any value enabled it. The pipx.interpreter.find_python_interpreter keyword fetch_missing_python: bool is replaced by fetch_python: FetchPythonOptions. (#1663) by @13steinj and @gaborbernatAdd pipx help and pipx help aliases for existing help output.
<a name="release-1-11-2-added"></a>
pipx help and pipx help <command> aliases for existing help output. (#1535)Add pipx help and pipx help <command> aliases for existing help output. (1535)
Drop support for Python 3.9. (1786) by henryiii
Replace if/elif command dispatch in main.py with argparse set_defaults. (1794)
Ignore PIP_TARGET environment variable to prevent pip from installing outside the venv.
<a name="release-1-11-1-fixed"></a>
PIP_TARGET environment variable to prevent pip from installing outside the venv. (#735)pipx install failing on Windows when the username contains non-Latin characters (e.g. cyrillic, Chinese). (#780)upgrade when install detects an existing installation. (#795)--verbose and --quiet flags before the subcommand are no longer silently ignored. (#1282)--include-deps. (#1364)setuptools from shared libs to prevent version conflicts when app venvs use a different Python. (#1539)uninject from removing dependencies still needed by other packages in the venv. (#1672)Add PIPX_MAX_LOGS environment variable to configure the maximum number of log files to keep.
<a name="release-1-11-0-added"></a>
PIPX_MAX_LOGS environment variable to configure the maximum number of log files to keep. (#1570)<a name="release-1-11-0-fixed"></a>
--pip-args to be passed to upgrade-all. (#1503)--pip-args='-c <url>' breaking when constraint target is a URL instead of a local path. (#1582)PIP_KEYRING_PROVIDER=subprocess (#1603)pip list command failures (#1698)<a name="release-1-11-0-documentation"></a>
--suffix help text. (#1621)Add PIPX_MAX_LOGS environment variable to configure the maximum number of log files to keep. (1570)
Allow --pip-args to be passed to upgrade-all. (1503)
Fix --pip-args='-c <url>' breaking when constraint target is a URL instead of a local path. (1582)
Enable keyring authentication for private package indexes by setting PIP_KEYRING_PROVIDER=subprocess (1603)
Added error handling for pip list command failures (1698)
Remove outdated "experimental" note from --suffix help text. (1621)
Use stored pip_args from install metadata when running pipx upgrade without explicit --pip-args
<a name="release-1-10-1-fixed"></a>
pipx upgrade without explicit --pip-args (#1441)--global flag being silently ignored when placed before the subcommand (#1443)--quiet flag in install and suppress animations and success messages (#1508)upgrade and show helpful error instead of crashing (#1602)uninstall, reinstall, and other package-name arguments (#1718)Use stored pip_args from install metadata when running pipx upgrade without explicit --pip-args (1441)
Fix --global flag being silently ignored when placed before the subcommand (1443)
Respect --quiet flag in install and suppress animations and success messages (1508)
Catch missing Python interpreter in upgrade and show helpful error instead of crashing (1602)
Prevent data loss by rejecting relative paths in uninstall, reinstall, and other package-name arguments (1718)
Add --with flag to pipx run to allow injecting dependencies
<a name="release-1-10-0-added"></a>
--with flag to pipx run to allow injecting dependencies (#1607)<a name="release-1-10-0-fixed"></a>
pipx upgrade "coverage[toml]"). (#925)pipx run <(pbpaste)) (#1293)pipx runpip to split single string arguments. (#1520)Add --with flag to pipx run to allow injecting dependencies (1607)
add more specific directions in the logs towards a resolution if you have a space in the PIX_HOME path (1634)
Fixed upgrade command failing when package name includes extras (e.g., pipx upgrade "coverage[toml]"). (925)
Fix run command with bash substitution (e.g. pipx run <(pbpaste)) (1293)
Allow pipx runpip to split single string arguments. (1520)
Fix handling of shared libraries when the original Python interpreter is removed on Windows by detecting stale venv references and recreating the shared libraries with the current Python. (1723)
Add completion choices for pipx environment --value.
<a name="release-1-9-0-added"></a>
pipx environment --value. (#1498)<a name="release-1-9-0-fixed"></a>
pipx reinstall: An exception will now be raised if package is pinned. (#1611)pipx run from leaving bad temporary venvs when first installation was unsuccessful. (#1709)Add completion choices for pipx environment --value. (1498)
Ignore recursive symlink loops in PIPX_BIN_DIR. (1592)
pipx reinstall: An exception will now be raised if package is pinned. (1611)
Stop pipx run from leaving bad temporary venvs when first installation was unsuccessful. (1709)
Rename environmental variable USE_EMOJI to PIPX_USE_EMOJI.
<a name="release-1-8-0-added"></a>
USE_EMOJI to PIPX_USE_EMOJI. (#1395)--all-shells flag to pipx ensurepath. (#1585)<a name="release-1-8-0-fixed"></a>
--fetch-missing-python works on Windows (#1521)upgrade-all. (#1565)pipx upgrade. (#1610)dependencies = []. (#1658) by @neutrinoceros<a name="release-1-8-0-documentation"></a>
/changelog/ and /contributing/ docs URLs (#1540)Rename environmental variable USE_EMOJI to PIPX_USE_EMOJI. (1395)
Add --all-shells flag to pipx ensurepath. (1585)
Add support for Python 3.13 (1647) by dukecat0
On Windows, no longer overwrite existing files on upgrade if source and destination are the same (683)
Update the logic of finding python interpreter such that --fetch-missing-python works on Windows (1521)
Fix no message displayed when no packages are upgraded with upgrade-all. (1565)
Fix incorrect order of flags when using pipx upgrade. (1610)
Update the archive name of build of Python for Windows (1630)
Set up standalone python fetching to use checksums directly from the GitHub API. (1652)
Fix running a script with explicitly empty dependencies = []. (1658) by neutrinoceros
Fix /changelog/ and /contributing/ docs URLs (1540)
Use minimum supported Python to build zipapp in release action such that tomli is included in it.
<a name="release-1-7-1-fixed"></a>
tomli is included in it. (#1514)Use minimum supported Python to build zipapp in release action such that tomli is included in it. (1514)
Add a --prepend option to the pipx ensurepath command to allow prepending pipx's location to PATH rather than appending to it. This is useful when you
<a name="release-1-7-0-added"></a>
--prepend option to the pipx ensurepath command to allow prepending pipx's location to PATH rather than appending to it. This is useful when you want to prioritize pipx's executables over other executables in your PATH. (#1451) by @agriyakhetarpal and @GitznikPIPX_GLOBAL_[HOME|BIN_DIR|MAN_DIR] in pipx environment. (#1492)PIPX_HOME_ALLOW_SPACE environment variable, to silence the spaces in pipx home path warning (#1320)<a name="release-1-7-0-fixed"></a>
pipx install operation via pip args (#1389)pipx install --global from installing files in ~/.local. (#1475)<a name="release-1-7-0-documentation"></a>
pipx pin and pipx unpin commands. (#1438) by @dukecat0docs directory. (#1479)Add a --prepend option to the pipx ensurepath command to allow prepending pipx's location to PATH rather than appending to it. This is useful when you want to prioritize pipx's executables over other executables in your PATH. (1451) by agriyakhetarpal and Gitznik
List PIPX_GLOBAL_[HOME|BIN_DIR|MAN_DIR] in pipx environment. (1492)
Introduce PIPX_HOME_ALLOW_SPACE environment variable, to silence the spaces in pipx home path warning (1320)
Fix passing constraints file path into pipx install operation via pip args (1389)
Stop pipx install --global from installing files in ~/.local. (1475)
Fix installation abortion on multiple packages when one or more are already installed. (1509)
Add help messages for pipx pin and pipx unpin commands. (1438) by dukecat0
Move all documentation files to the docs directory. (1479)
Add install-all command to install packages according to spec metadata file.
<a name="release-1-6-0-added"></a>
install-all command to install packages according to spec metadata file. (#687)pipx pin and pipx unpin commands, which can be used to pin or unpin the version of an installed package, so it will not be upgraded by pipx upgrade or pipx upgrade-all. (#891)--pinned to pipx list command for listing pinned packages only. (#891)pipx interpreter upgrade command to upgrade local standalone python in micro/patch level (#1249)--requirement option to inject command to read list of packages from a text file. (#1252) by @jamesmyatt, @chrysle and @huxuanpipx upgrade-shared command, to create/upgrade shared libraries as a standalone command. (#1316) by @mayeut and @chrysleupgrade command to accept multiple packages as arguments. (#1336)--python arg when py launcher is not available (#1342)install-all gather errors in batch (#1348) by @huxuan, @dukecat0 and @chrysle<a name="release-1-6-0-fixed"></a>
DEFAULT_PYTHON to the actual absolute path (#965)--force being passed. (#1300)--python and --force flag warning if both flags are present (#1304)pipx reinstall, as this might wreak havoc. (#1324)venv module arguments work with upgrade --install (#1344)--preinstall dependency instead of latest version (#1377)--global option into shared parser, such that it can be passed after the subcommand, for example pipx ensurepath --global. (#1397) by @dukecat0pipx run entry point if a local path was given as package. (#1422) by @chrysle and @huxuan<a name="release-1-6-0-documentation"></a>
pdm-backend. (#1312) by @pawamoyensure_path (#1346)Add install-all command to install packages according to spec metadata file. (687)
Introduce pipx pin and pipx unpin commands, which can be used to pin or unpin the version of an installed package, so it will not be upgraded by pipx upgrade or pipx upgrade-all. (891)
Add a new option --pinned to pipx list command for listing pinned packages only. (891)
Add pipx interpreter upgrade command to upgrade local standalone python in micro/patch level (1249)
Add --requirement option to inject command to read list of packages from a text file. (1252) by jamesmyatt, chrysle and huxuan
Add pipx upgrade-shared command, to create/upgrade shared libraries as a standalone command. (1316) by mayeut and chrysle
Allow upgrade command to accept multiple packages as arguments. (1336)
Support Python version for --python arg when py launcher is not available (1342)
Make install-all gather errors in batch (1348) by huxuan, dukecat0 and chrysle
Support python3.8 for standalone python builds (1375)
Resolve the DEFAULT_PYTHON to the actual absolute path (965)
Fix error log overwrite for "-all" batch operations. (1132)
Do not reinstall already injected packages without --force being passed. (1300)
Only show --python and --force flag warning if both flags are present (1304)
Don't allow paths to be passed into pipx reinstall, as this might wreak havoc. (1324)
Make the Python venv module arguments work with upgrade --install (1344)
Fix version check for standalone python (1349)
Validate package(s) argument should not be path(s). (1354)
Validate whether a package is an URL correctly. (1355)
Install specified version of --preinstall dependency instead of latest version (1377)
Move --global option into shared parser, such that it can be passed after the subcommand, for example pipx ensurepath --global. (1397) by dukecat0
Fix discovery of a pipx run entry point if a local path was given as package. (1422) by chrysle and huxuan
Create a dedicated section for manual pages and add an example with pdm-backend. (1312) by pawamoy
Add example, test and cli help description how to install multiple packages with the --preinstall flag (1321) by gempir
Refine docs generation script and template. (1325)
Add a note about sourcing the shell config file for ensure_path (1346)
Deprecate --skip-maintenance flag of pipx list; maintenance is now never executed there (#1256) by @Arpafaucon
<a name="release-1-5-0-added"></a>
--global option to pipx commands.
--fetch-missing-python flag to all commands that accept a --python flag.
--install option to pipx upgrade command.
<a name="release-1-5-0-fixed"></a>
pip arguments when upgrading shared libraries. (#964)pipx run <scriptname> (#1191) by @henryiii and @flying-sheeppipx install is run without arguments. (#1266) by @dukecat0-q flags by discarding exceeding values (#1283)<a name="release-1-5-0-documentation"></a>
pipx install command description. (#1307) by @sgryjp<a name="release-1-5-0-deprecated"></a>
--skip-maintenance flag of pipx list; maintenance is now never executed there (#1256) by @ArpafauconAdd --global option to pipx commands.
This will run the action in a global scope and affect environment for all system users. (754)
Add a --fetch-missing-python flag to all commands that accept a --python flag.
When combined, this will automatically download a standalone copy of the requested python version if it's not already available on the user's system. (1242)
Add commands to list and prune standalone interpreters (1248)
Revert platform-specific directories on MacOS and Windows
They were leading to a lot of issues with Windows sandboxing and spaces in shebangs on MacOS. (1257)
Add --install option to pipx upgrade command.
This will install the package given as argument if it is not already installed. (1262)
Correctly resolve home directory in pipx directory environment variables. (94)
Pass through pip arguments when upgrading shared libraries. (964)
Fix installation issues when files in the working directory interfere with venv creation process. (1091)
Report correct filename in tracebacks with pipx run <scriptname> (1191) by henryiii and flying-sheep
Let self-managed pipx uninstall itself on windows again. (1203)
Fix path resolution for python executables looked up in PATH on windows. (1205)
Display help message when pipx install is run without arguments. (1266) by dukecat0
Fix crashes due to superfluous -q flags by discarding exceeding values (1283)
Update the completion instructions for zipapp users. (1072)
Update the example for running scripts with dependencies. (1227)
Update the docs for package developers on the use of configuration using pyproject.toml (1229)
Add installation instructions for Fedora (1239) by markmc
Update the examples for installation from local dir (1277)
Fix inconsistent wording in pipx install command description. (1307) by sgryjp
Deprecate --skip-maintenance flag of pipx list; maintenance is now never executed there (1256) by Arpafaucon
Autofix python version for pylauncher, when version is provided prefixed with python
<a name="release-1-4-3-fixed"></a>
python (#1150)<a name="release-1-4-3-documentation"></a>
<a name="release-1-4-3-packaging"></a>
Autofix python version for pylauncher, when version is provided prefixed with python (1150)
Provide useful error messages when unresolvable python version is passed (1150)
Introduce towncrier for managing the changelog (1161)
Add workaround for using pipx applications in shebang under macOS (1198)
Support building pipx wheels with setuptools-scm<7, such as on FreeBSD. (1208) by henryiii
One column per quarter.