NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI
PyPI, #1531 most downloaded on PyPI
Python Development Workflow for Humans.
Latest stable
2026.11.0
Last release 13 days ago
09 Nov 2026
Release timing varies
gaps range from 9 days to 3 months
Nearly every release is documented
notes for 60 of the last 60 stable releases
3 versions withdrawn
withdrawn after publishing
10 years old
431 releases · first in 2017
Drag across the ruler to compare, or tap a release to open it.
Added a new uv resolver backend as an alternative to the default pip-based resolver, providing faster dependency resolution
uv resolver backend as an alternative to the default pip-based resolver, providing faster dependency resolutionpipenv scan, preserving stderr output appropriately--no-lock🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.10.6...v2026.11.0
uv resolver backend. pipenv lock --backend uv, PIPENV_RESOLVER=uv or resolver_backend = "uv" in the [pipenv] section of the Pipfile resolves dependencies with uv <https://docs.astral.sh/uv/>_ (which must be on $PATH) while keeping pipenv's index restriction, hashes and markers. See the new "Resolver Backends" documentation page. #6109 <https://github.com/pypa/pipenv/issues/6109>_RequirementError when no requirement is given and in
Lockfile.from_data when the project directory is missing, and removed a stray
!s from the UninstallError message. #6781 <https://github.com/pypa/pipenv/issues/6781>_pipenv requirements --no-lock dropping the environment markers of VCS entries. #6782 <https://github.com/pypa/pipenv/issues/6782>_pipenv --quiet check --scan
if the scan fails, while keeping successful quiet scans free of stderr warnings. #quiet-scan-stderr <https://github.com/pypa/pipenv/issues/quiet-scan-stderr>_#6780 <https://github.com/pypa/pipenv/issues/6780>_Your coding agent can read these notes before it upgrades. Set up the MCP server →
Exit with a non-zero status code when safety cannot be installed or run during check/scan, ensuring failures are properly signaled to calling processe
safety cannot be installed or run during check/scan, ensuring failures are properly signaled to calling processesPipfile as UTF-8 in check, scan, and --support commands, preventing errors with non-ASCII characters in Pipfile content🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.10.5...v2026.10.6
pipenv check and pipenv scan exiting with status 0 when safety could not be installed (or was still missing after the install): they now exit with status 1, so CI no longer passes without having scanned anything.pipenv check, pipenv scan and pipenv --support now read the Pipfile
and Pipfile.lock as UTF-8 (with or without a BOM) instead of the locale encoding.pipenv graph no longer fails with UnicodeEncodeError when its output is piped or redirected on Windows (pipenv graph > deps.txt): the tree is drawn with ASCII characters when stdout cannot encode box-drawing characters. #5929 <https://github.com/pypa/pipenv/issues/5929>_Raised minimum versions of dependencies to address known security vulnerabilities
--trusted-host arguments being flagged as secrets in CodeQL security scanningpipenv update to correctly handle requirement specifiers as argumentsrequirements command to emit --trusted-host for sources with verify_ssl = falserequirements command to correctly join os_markers and markers with andrequirements command to preserve markers for git/VCS entriesuninstall command to exit with a non-zero code when pip uninstall failsuninstall command to report why it exits 1 when no virtualenv existspylock.tomldevelop and requires-python as python_versionpipenv version would be tested than the checked-out one--trusted-host logic to be shared between requirements and install, preserving environment-variable-defined hosts🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.10.4...v2026.10.5
#6771 <https://github.com/pypa/pipenv/issues/6771>_pipenv update conflict detection and extra-category lookup for package arguments with extras or version ranges (requests[socks]==2.0, pkg>=2): the package name is now parsed as a requirement instead of splitting on =, and only exact pins are checked for conflicts.pylock.toml.
Apply the selected groups when validating and installing packages, and retain each category's environment markers for shared dependencies.
Parse group markers independently of whitespace so dev-only packages cannot be moved into the default category by compact marker syntax.
Convert simple requires-python specifiers to a plain python_version or python_full_version. #6758 <https://github.com/pypa/pipenv/issues/6758>_pylock.toml and record each group's original category under [tool.pipenv.categories] so reading the file restores the same categories, including --dev-groups aliases as develop.
Generating pylock.toml now fails when two categories, or a category and one of the --dev-groups, map to the same dependency group, instead of merging them. #6759 <https://github.com/pypa/pipenv/issues/6759>_pipenv requirements now keeps the environment marker of git/VCS dependencies, so they are no longer installed on platforms the Pipfile.lock excludes. #6760 <https://github.com/pypa/pipenv/issues/6760>_pipenv requirements now prints --trusted-host for sources with verify_ssl = false, as pipenv install passes it to pip. #6761 <https://github.com/pypa/pipenv/issues/6761>_pipenv uninstall now exits with a non-zero status when pip uninstall fails for a package. #6762 <https://github.com/pypa/pipenv/issues/6762>_#6661 <https://github.com/pypa/pipenv/issues/6661>_Added interactive pipenv init command for creating a Pipfile with guided prompts
pipenv init command for creating a Pipfile with guided promptspipenv install -r to decode requirements files using the same encoding detection as pippipenv audit to exit with a non-zero status code when pip-audit cannot be runpipenv graph to print the missing virtualenv warning to stderr instead of stdoutpipenv outdated to correctly interpolate the required version in skipped-update messagespipenv install to restore the Pipfile byte-for-byte when installation fails, including rolling back changes made by pipenv init🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.10.3...v2026.10.4
pipenv init, which creates a Pipfile for a new project through a short dialog (requirements.txt import, Python version, package index, packages and dev packages, and whether to create the virtualenv and lock). --yes accepts the defaults without prompting, and --install / --no-install control the follow-up install. If that install fails, the new Pipfile is removed so pipenv init can be run again. #5792 <https://github.com/pypa/pipenv/issues/5792>_pipenv install <package> (for example a package that doesn't exist, or a version that can't be resolved) now restores the Pipfile exactly as it was. Previously a lock failure left the new entry in the Pipfile, and a failed upgrade of a package already in the Pipfile could remove that package entirely. An unresolvable dependency also no longer prints a Python traceback after the resolver's error message; pass --verbose to see it. #6747 <https://github.com/pypa/pipenv/issues/6747>_pipenv crashing with UnicodeDecodeError, or rewriting the Pipfile in the locale encoding (such as cp932 on Japanese Windows), when the Pipfile contains non-ASCII text such as a comment or a path.
The Pipfile is now always read as utf-8-sig and written as UTF-8, and a Pipfile.lock saved with a byte order mark is no longer treated as corrupt and moved to Pipfile.lock.bak. #6756 <https://github.com/pypa/pipenv/issues/6756>_Pipfile.lock and pylock.toml if replacement fails,
and avoid exposing a missing lockfile to concurrent readers. #6757 <https://github.com/pypa/pipenv/issues/6757>_pipenv audit now exits with status 1 instead of 0 when pip-audit could not be installed, was declined, or is still missing after installing, so CI no longer treats an audit that never ran as a pass. #6763 <https://github.com/pypa/pipenv/issues/6763>_pipenv install -r now reads the requirements file the way pip does (UTF-8/UTF-16 BOMs and PEP 263 coding comments) instead of the locale encoding when it looks for -i, --extra-index-url and --trusted-host lines. #6764 <https://github.com/pypa/pipenv/issues/6764>_pipenv graph in a project without a virtualenv now prints the "No virtualenv has been created" warning and exits with 1 instead of failing with an AttributeError. #6765 <https://github.com/pypa/pipenv/issues/6765>_pipenv outdated now shows the version that a dependent package requires in the "Skipped Update" message instead of the literal {rdeps['required']}. #6766 <https://github.com/pypa/pipenv/issues/6766>_Bump certifi in the /examples directory to address potential security vulnerabilities
rmtree test shim to ensure compatibility with Python 3.14.9pip dependency to latest version (includes 3 updates)certifi in the /examples directory to address potential security vulnerabilities🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.10.2...v2026.10.3
rmtree test shim to ensure compatibility with Python 3.14.9pip dependency to latest version (includes 3 updates)certifi in the /examples directory to address potential security vulnerabilities🔗 Full Changelog: v2026.10.2...v2026.10.3
Read Pipfile, Pipfile.lock, pylock.toml, and pyproject.toml as UTF-8 with BOM support (utf-8-sig) to handle files with byte order marks
Pipfile, Pipfile.lock, pylock.toml, and pyproject.toml as UTF-8 with BOM support (utf-8-sig) to handle files with byte order markstasks package in the sdist distribution🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.10.1...v2026.10.2
tasks package in the sdist so that the shipped tests/unit/test_release_tasks.py can import it when the test suite is run from a source distribution. #6748 <https://github.com/pypa/pipenv/issues/6748>_pipenv failing to read a Pipfile, Pipfile.lock, pylock.toml or pyproject.toml that was saved as UTF-8 with a byte order mark (BOM), which editors such as Windows Notepad add.
The files are now decoded as utf-8-sig. #6750 <https://github.com/pypa/pipenv/issues/6750>_pipenv/vendor and pipenv/patched) as a pre-commit hook, which also gates CI. Existing type errors were fixed, mostly by correcting annotations and converting legacy # type: comments to inline annotations.Skip * (wildcard) versions when pinning resolved default dependencies as constraints, preventing invalid constraint generation
* (wildcard) versions when pinning resolved default dependencies as constraints, preventing invalid constraint generationpylock.toml entry for packages that are locked in both default and develop groups, avoiding duplicate entries$VAR references in source URLs when generating requirements with --no-lock, ensuring proper shell variable expansionpylock.toml markers for dependencies that reference a dependency grouppylock.toml output from locked package data🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.10.0...v2026.10.1
pylock.toml files
by matching locked hashes against the package index.
Avoid fabricated wheel entries when an artifact cannot be identified. #6738 <https://github.com/pypa/pipenv/issues/6738>_pipenv requirements --no-lock now writes a bare $VAR in a source URL as ${VAR}, as pipenv requirements
already does from the lockfile, so pip can expand it. Previously the --no-lock output kept $VAR, which pip leaves
unexpanded. #6741 <https://github.com/pypa/pipenv/issues/6741>_pylock.toml markers that also name a dependency group,
such as sys_platform == "win32" and "dev" in dependency_groups as written by pdm export -f pylock.
Previously the whole marker was dropped, so installing from such a pylock.toml installed those packages on every platform. #6742 <https://github.com/pypa/pipenv/issues/6742>_pylock.toml entry for a package that Pipfile.lock lists in both default and develop.
Previously both copies were written, so installing with the dev group failed: uv pip install -r pylock.toml --group dev
reported multiple active entries, and Pipenv itself could not load the file (has 2 entries that match the environment). #6743 <https://github.com/pypa/pipenv/issues/6743>_pipenv lock failing with Invalid requirement: 'colorama*' when a default package has markers that exclude the current platform,
such as colorama = {version = "*", markers = "sys_platform == 'win32'"}, and the Pipfile also has [dev-packages].
The default section's locked "*" entry was turned into an invalid constraint for the develop resolution. #6744 <https://github.com/pypa/pipenv/issues/6744>_Support file:// URLs as package index and mirror sources
file:// URLs as package index and mirror sourcespylock.toml lock versions with a warning instead of failingpylock.toml requires-python and environments fields before installingpylock.tomlpylock.tomlfile:// requirements.txt URLs to paths before resolving--skip-lock pathfile:// Pipfile entries being mis-handled as filesystem paths on Windowsfile=...+extras=[...] dependencies-i <url> replace the default index rather than add to it--trusted-host for hostless source URLs regardless of verify_sslverify_ssl=false handling on hardcoded file:// source blockspackaging to 26.3, plette to 2.4.0, build to 1.6.1, pyproject_hooks to 1.3.3, dotenv to 1.2.4tomli for hatchling's build isolation on Python < 3.11VCS_SCHEMES into pipenv.utils.constantsfile://-based fixtures🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.9.1...v2026.10.0
pylock.toml whose requires-python, environments, or a package's requires-python excludes the target Python, as PEP 751 requires. #6732 <https://github.com/pypa/pipenv/issues/6732>_pylock.toml lists a package more than once,
instead of the last entry, and raise an error when more than one entry matches. #6734 <https://github.com/pypa/pipenv/issues/6734>_pylock.toml with a newer minor lock-version (e.g. 1.1) with a warning instead of rejecting it,
as PEP 751 requires an error only for an unsupported major version. #6735 <https://github.com/pypa/pipenv/issues/6735>_pylock.toml as PEP 751 directory, vcs and archive
sources, and install them from those sources. Previously they were written as plain index packages, so installing
from pylock.toml looked the name up on the package index. #6737 <https://github.com/pypa/pipenv/issues/6737>_build to 1.6.1, packaging to 26.3,
pyproject_hooks to 1.3.3, python-dotenv to 1.2.4, and
plette to 2.4.0.Fixed a crash in the pure-Python resolver backend when checking hashes for sdist packages
resolver_backend is set in [pipenv] configuration outside of a lock operationresolver_backend setting in [pipenv] is now honored consistently outside of lock operationsfind_matches results during backtracking and caching parsed package manifests🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.9.0...v2026.9.1
'frozenset' object has no attribute 'get' when it has to build an sdist for metadata. The
SHA-256 check on the downloaded sdist now reads the candidate's hashes in
the shape the simple-API parsers produce, so the check actually runs.[pipenv] resolver_backend in the Pipfile is now honored by pipenv update, pipenv upgrade and pipenv uninstall. Previously only
pipenv lock read the documented key; the other commands only checked
the older [pipenv] resolver alias and silently re-locked with the pip
backend.pip and pure-python). benchmarks/benchmark.py accepts
--backend, which selects the backend through [pipenv] resolver_backend in the benchmark Pipfile.`pipenv sync --clean`: New flag to automatically uninstall packages that are present in the environment but missing from the lockfile, keeping environ
pipenv sync --clean: New flag to automatically uninstall packages that are present in the environment but missing from the lockfile, keeping environments in sync with declared dependencies--backend CLI flag and [pipenv] resolver_backend Pipfile setting to opt into an alternative pure-Python dependency resolver (Initiative G), featuring:
Requirement.introducing_markerpipenv install now persists configuration settings on a per-package basis, isolating options between packages[pipenv] package_name_case Pipfile setting (previously controlled by PIPENV_RECASE_PIPFILE env var); recasing is disabled by default for performance>=21.14.6200_000 to handle complex dependency graphsnot in exclusions for python_version are no longer incorrectly collapsed; legacy not in exclusions are preserved exactly, and == version groups are version-sortedpipenv sync --dry-run: No longer uninstalls packages; all lockfile sections are preserved during dry runspipenv --envs: Fixed broken documentation URL to point to a valid page--upgrade flag dropped from pip install calls during syncfind_matches/get_dependencies and applies pip's narrow requirement selectionpipenv sync does not remove packages missing from the lockfile (addressed by new --clean flag)🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.8.0...v2026.9.0
The pure-Python resolver backend ([pipenv] resolver_backend = "pure-python") now builds sdists inside a PEP 517 isolated env via
the (newly-vendored) PyPA :pypi:build library. Previously the
sdist METADATA hook ran in pipenv's own interpreter, which crashed
on import for any package whose declared
[build-system].build-backend (e.g. poetry-core,
hatchling, flit-core) wasn't already installed. The
resolver now spins up a throwaway venv per build, installs the
project's [build-system].requires plus any
get_requires_for_build("wheel") extras, then invokes the
backend's prepare_metadata_for_build_wheel hook against that
env. :pypi:build lives at pipenv/vendor/build so the
resolver subprocess can import it from the project venv's Python
without an extra runtime dep.
pipenv install and pipenv sync now pre-fetch wheels in
parallel from the configured indexes BEFORE invoking pip install,
populating a --find-links directory pip then reads from. Pip's
own install step is sequential, so on a cold pip cache the network
download phase dominates wall time — the sentry-base benchmark's
151 wheels spent ~12 s of pure-network time in pip's subprocess
before this change. Pre-fetching uses the resolver's existing
PEP 691 client + ParallelFetcher (urllib3 connection-pool capped
at 16 workers, mirroring the established resolver concurrency
contract) and verifies every downloaded body's SHA-256 against the
lockfile's pinned hashes before exposing it to pip.
The pre-fetch is best-effort: any per-package failure (missing
target-platform wheel, hash mismatch, network hiccup) falls through
silently and pip downloads that package via the index as usual.
The shortcut only fires when the install is driven from a
hash-pinned lockfile (i.e. pipenv sync or pipenv install
without --skip-lock); unpinned installs keep the legacy
behaviour.
Bench impact on the sentry-base fixture (Python 3.11 venv, 151 wheels, cold pip cache):
--find-links
read path is cheaper than its HTTP-cache lookup, so warm-cache
installs benefit too).Persist per-package pip build arguments from pipenv install --config-settings
in the Pipfile and lockfile so editable builds can be reproduced by later
installs and syncs. #5740 <https://github.com/pypa/pipenv/issues/5740>_
Added pipenv sync --clean, which uninstalls packages not in the lock file
after installing, equivalent to pipenv sync && pipenv clean. As with
pipenv clean, packages locked in any lockfile section are kept. It is
refused with --system. pipenv clean --bare is now honoured, and
pipenv clean no longer removes packages from lockfile sections that the
Pipfile does not declare. #6724 <https://github.com/pypa/pipenv/issues/6724>_
Pipfile name recasing is now opt-in via [pipenv] package_name_case.
Previously, every pipenv install walked packages /
dev-packages and made one synchronous PyPI HTTP request per unknown
package name to learn its display capitalization, then rewrote the
Pipfile entry to match. On a fresh install -r requirements.txt of
~100 packages this added roughly 3 seconds of sequential network
latency on top of the resolve, regardless of cache state.
The new package_name_case setting accepts:
"off" — default; package names you wrote into your
Pipfile are preserved as-is. PEP 503 normalization still governs
resolution, so behavior is unchanged for matching purposes."canonical" — apply PEP 503 normalization
(packaging.utils.canonicalize_name) to every entry; fully offline."pypi" — restore the prior behavior, fetching display
capitalization from PyPI per name.The toggle lives in the Pipfile rather than in an environment variable
so every contributor on the project gets the same behaviour and
pipenv install does not bounce the Pipfile back and forth between
commits when teammates have different shell defaults.
pip install invocations driven by pipenv sync no longer
pass --upgrade. The flag was hardcoded True historically as
a safety net to force a re-install when a package was already
present at a different version, but with --no-deps (always set
for sync) plus explicit pkg==X.Y.Z lines and the upstream
Environment.is_satisfied filter that already runs before the
batch is handed to pip, --upgrade is redundant — it forces pip
to do a per-package metadata check that costs measurable wall time
when the lockfile has many entries. pipenv install
(Pipfile-driven, may need to downgrade) still passes --upgrade.
The pure-Python resolver backend ([pipenv] resolver_backend = "pure-python") now correctly threads extras
(pkg[extra1,extra2]) through the resolver pipeline so
marker-gated transitive dependencies appear in the lockfile. For
example, psycopg[binary] now pulls psycopg-binary as a
locked transitive (it didn't before, because the wire-shape parser
dropped the extras section before the resolver ever saw it).
Five round-trip points were updated together so the bench fixture keeps converging while T_PARITY_REAL hits 10/10 parity with pip:
PurePythonBackend._spec_value_to_pipfile_entry parses the
[extras] segment of a wire-shape pip-install line and
surfaces it via the dict-form Pipfile-entry shape that
Requirement.from_pipfile_entry already accepts.
PurePythonProvider.find_matches clones the filtered candidate
set with extras=identifier_extras so T7's
get_dependencies sees the right parent_extras context
when iterating Requires-Dist lines.
PurePythonProvider.get_dependencies strips the
extra == X clauses from a transitive's runtime marker via a
new _strip_extra_clauses helper. The extras-gating role was
already consumed at emission time; carrying the clause onto
Requirement.marker made every candidate fail the runtime
marker re-evaluation. introducing_marker keeps the original
for the lockfile emitter.
PurePythonProvider.get_dependencies also emits a synthetic
base-version requirement when the parent candidate carries
extras — pins the bare (name, frozenset()) identifier to the
exact version of the extras-flavoured candidate. Mirrors pip's
ExtrasCandidate.iter_dependencies shape and prevents the
bare and extras identifier streams from diverging.
PurePythonProvider now implements
narrow_requirement_selection (mirroring pip's
PipProvider.narrow_requirement_selection) plus a promote-to-
front polarity flip on get_preference's leading slot. The
wider transitive constraint graph that extras propagation
surfaces (overlapping upper bounds on protobuf / grpcio /
grpcio-status from the sentry-protos + google-cloud-* fleet)
needed pip-style conflict tracking to converge — without it the
sentry-base bench fixture thrashed indefinitely. The bench now
completes in ~40 s (down from ~2 min baseline) with
byte-identical hash to the pip backend.
T_PARITY_REAL hits 10/10 byte-identical parity with the pip
backend across the design's wheel-heavy combos
(django+psycopg[binary], flask+gunicorn,
fastapi+uvicorn, requests+httpx, pandas+numpy,
pytest+pytest-cov, sqlalchemy+alembic,
cryptography+pyopenssl, boto3+botocore, click+rich).
The pure-Python resolver backend ([pipenv] resolver_backend = "pure-python") now mirrors pip's two-pass prerelease filter: the
first pass strictly excludes prereleases (matching pip's
CandidateEvaluator.get_applicable_candidates default), and only
falls back to admitting them when no stable version satisfies the
merged specifier. Previously every prerelease leaked through under
plain >=X constraints because the per-candidate
SpecifierSet.contains(..., prereleases=None) shape applies
PEP 440's "no final release matched — accept the prerelease"
fallback on a one-element iterable; pip dodges this by filtering the
full candidate list at once. Bench-fixture trigger: billiard,
hiredis, and sentry-sdk were resolving to pre-release
versions (4.3.0rc1, 3.4.0.dev0, 3.0.0a7) where pip
picked the stable below.
Fixed requirements export to respect an explicitly selected PyPI mirror without
changing the Pipfile or lockfile, while retaining private package indexes. #5270 <https://github.com/pypa/pipenv/issues/5270>_
Requires-Python exclusions such as !=3.0.*, !=3.1.* are now translated
into one python_version != '...' clause per version instead of being
collapsed into python_version not in '3.0, 3.1'. Multiple == versions
are likewise rendered as a parenthesized or group rather than in.
Marker in/not in use string containment, so the collapsed forms were
not valid version comparisons (for example '3.1' in '3.10, 3.11' is true).
Existing markers that use not in with python_version are now parsed
correctly when merging markers, keeping exactly the listed versions. #6727 <https://github.com/pypa/pipenv/issues/6727>_
pipenv --envs.
It pointed at advanced/#configuration-with-environment-variables,
which 404s: the docs are served as .html pages and the environment
variable reference now lives on configuration.html. #6718 <https://github.com/pypa/pipenv/issues/6718>_pipenv sync does not uninstall packages missing from
Pipfile.lock, cross-linked sync and clean, and added the
pipenv sync && pipenv clean pattern to the deployment workflow docs. #6723 <https://github.com/pypa/pipenv/issues/6723>_Parallel index manifest prefetching (PIPENV_PREFETCH_INDEX_MANIFESTS): New experimental feature that fetches package index manifests concurrently duri
PIPENV_PREFETCH_INDEX_MANIFESTS): New experimental feature that fetches package index manifests concurrently during lock operations, significantly reducing resolution time for large dependency setsParsedManifestCache): JSON-on-disk cache with TTL and atomic writes to avoid redundant index fetches across lock operationsverify_ssl fan-out for prefetcher: Each index source now independently respects its SSL verification and certificate settings during parallel prefetchpeek_etag stale-cache short-circuit: Resolver can now skip full manifest fetches when ETags indicate cached data is still freshprefetch_index_manifests setting: New boolean configuration option to enable/disable the parallel prefetch featureProject: Internal refactor completing Initiative D; project.build_script and related attributes now live on project.pipfileProject: Lockfile state management is now a dedicated subsystemunpack_url / get_http_url moved to pipenv/utils/unpack.py; legacy requirementslib.py removedPipfile.lock pins are fed as pip constraints on warm relock to speed up re-locking (reverted and re-landed with fixes)os.replace is retried on ERROR_ACCESS_DENIED with a wall-clock budget, fixing cache write failures on Windowsresolver_backend is now correctly plumbed through the venv_resolve_deps call chainproject.build_script call sites migrated to project.pipfile.build_scripttest_lockfile_location_is_pipfile_plus_lock made OS-portableInstallCommand, unpack, Downloader, network imports) to improve startup performance🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.7.1...v2026.8.0
--resolver NAME CLI flag, PIPENV_RESOLVER environment variable,
and [pipenv] resolver Pipfile setting are now recognized, but only
pip (the default) is shipped in this release. Selecting an unknown
backend will produce a clear error message. Future releases will add
additional backends. #T_F.5 <https://github.com/pypa/pipenv/issues/T_F.5>_pipenv/resolver/. Initiative G
phase 1 ships the standalone surface; no integration yet. Phase 2
(cache-prime bridge) and Phase 3 (full backend) will wire it in.
pipenv lock --clear and pipenv install --clear now invalidate
this parsed-manifest cache in addition to pip's HTTP cache. #initiative-g-phase1-pep691-client <https://github.com/pypa/pipenv/issues/initiative-g-phase1-pep691-client>_[pipenv] prefetch_index_manifests opt-in setting (also
PIPENV_PREFETCH_INDEX_MANIFESTS=1) that pre-fetches simple-API
index pages for top-level Pipfile packages in parallel before the
resolver runs. Most beneficial on cold caches or slow networks;
off-by-default because warm-cache dev machines see neutral-to-
slightly-slower behaviour. Initiative G phase 2. #initiative-g-phase2-prefetch-bridge <https://github.com/pypa/pipenv/issues/initiative-g-phase2-prefetch-bridge>_odin~=2.11 to 2.11rc3 before the 2.11 final release is available. #6701 <https://github.com/pypa/pipenv/issues/6701>_pipenv remove instead of the deprecated pipenv --rm flag. #6704 <https://github.com/pypa/pipenv/issues/6704>_#6711 <https://github.com/pypa/pipenv/issues/6711>_#6712 <https://github.com/pypa/pipenv/issues/6712>_Fixed host package leakage into project installs, preventing system-level packages from incorrectly being available in virtual environments
🔗 Full Changelog: v2026.7.0...v2026.7.1
cool-down-period in the [pipenv] section of the Pipfile.
Setting cool-down-period = "30d" instructs the resolver to only consider
package versions uploaded at least the specified number of days ago, via pip's
--uploaded-prior-to flag.pipenv install, pipenv lock, and pipenv sync. A hung mirror or
stuck pip download previously caused the resolver to block forever from
the user's perspective; the wait is now bounded by
PIPENV_RESOLVER_TIMEOUT_S (default 1800 seconds = 30 minutes,
chosen generously so normal resolutions are unaffected). On timeout the
subprocess is killed and a clear error is surfaced that names the
environment variable so users with legitimately large resolutions can
extend it.#T_F.3 <https://github.com/pypa/pipenv/issues/T_F.3>_[pipenv] resolver_timeout_seconds (Pipfile) >
PIPENV_RESOLVER_TIMEOUT_S (env var) > default (1800 seconds), and
is stamped onto RequestMetadata.deadline_seconds so the resolver
subprocess sees the same value the parent uses for
subprocess.wait(timeout=...). A hung resolver is now killed and a
structured error surfaced naming the override, instead of hanging
indefinitely. The in-process debug branch
(PIPENV_RESOLVER_PARENT_PYTHON=1) enforces the same deadline via
SIGALRM on Unix; Windows continues to rely on the subprocess
path for enforcement. #T_F.6 <https://github.com/pypa/pipenv/issues/T_F.6>_pipenv.utils.dependencies.pep423_name whose
scheme-token guard had an inverted predicate, making the branch that
preserves URL/VCS specifiers (e.g. git+ssh://host/path/some_repo)
from underscore-mangling unreachable. The predicate is now correct;
bare package names continue to be lowercased and have _ rewritten
to - as before. The sibling helper normalize_name in
pipenv.utils.requirements has been removed and its four callers
migrated to pep423_name.[[source]] URLs use
environment-variable placeholders. The GHSA-8xgg-v3jj-95m2 fix moved
credentials off pip's argv onto a merged netrc, but
write_credentials_netrc wrote our Pipfile-derived machine blocks
BEFORE the appended user netrc — and netrc.authenticators() returns
the LAST matching entry, so a stale system entry for the same host
silently overrode the freshly-expanded creds. Our blocks now come AFTER
the user's existing content. Additionally, the pylock.toml reader
now runs expand_url_credentials over its sources so users with
[pipenv] use_pylock = true see the same env-var expansion that
Pipfile.lock reads have always had. #6670 <https://github.com/pypa/pipenv/issues/6670>_pipenv update (no args) semantics of lock + sync.
Since 2026.0.0, pipenv update only re-resolved Pipfile entries whose
locked version no longer satisfied the Pipfile specifier, so relaxing a
pin (e.g. urllib3 = "<2.7.0" → urllib3 = "*") would not pick up
newer allowed releases — the lockfile silently stayed at the existing
pin. pipenv update now routes through do_lock when no packages
are given, re-resolving every Pipfile entry. The targeted
pipenv update <pkg> path is unchanged. #6672 <https://github.com/pypa/pipenv/issues/6672>_PIPENV_PYPI_MIRROR with embedded credentials (e.g.
https://user:pass@mirror.example.com). The GHSA-8xgg-v3jj-95m2 fix moved
credentials off pip's argv onto a temporary netrc, but the resolver's netrc
was written from the un-mirrored Pipfile sources, so the mirror's credentials
were dropped and resolution failed with 401 / ResolutionFailure. The
resolver netrc now applies the same PIPENV_PYPI_MIRROR substitution the
resolver subprocess uses, so the mirror credentials reach pip again. #6677 <https://github.com/pypa/pipenv/issues/6677>_python_version such as python_version = "3" in the Pipfile [requires] section, which the documentation lists as
valid. The version check added in 6535 compared the major and minor components
whenever fewer than three were given, but "3" parses to 3.0, so every
3.x interpreter but 3.0 was reported as a mismatch. That produced a spurious
warning on install and a fatal DeployException under --deploy. Only the
components actually given are compared now, so "3" matches any 3.x while
"3.13" and "3.13.1" keep their existing meaning. #6687 <https://github.com/pypa/pipenv/issues/6687>_cool-down-period locking to use package links from indexes that do
not expose upload-time metadata, while retaining the filter for indexes that do. #6691 <https://github.com/pypa/pipenv/issues/6691>_#6698 <https://github.com/pypa/pipenv/issues/6698>_plette to 2.2.1.pip to 26.1.2 and refresh vendored libraries:
pipdeptree to 3.1.0, packaging to 26.2,
pythonfinder to 3.0.4, and tomlkit to 0.15.0.
Also harden is_within_directory() in patched pip to use
os.path.commonpath() instead of startswith, fixing a
containment check edge case for root directories and Windows
drive mismatches. #6680 <https://github.com/pypa/pipenv/issues/6680>_urllib3 in patched pip to 2.7.0 (fixes GHSA-qccp-gfcp-xxvc,
sensitive headers forwarded across origins in proxied low-level redirects).
Raise minimum virtualenv requirement from >=20.24.2 to >=20.26.6
(fixes GHSA-rqc4-2hc7-8c8v, command injection through activation scripts).
The three other urllib3 CVEs reported in this issue (GHSA-2xpw-w6gg-jr37,
GHSA-38jv-5279-wg99, GHSA-gm62-xv2j-4w53) were already resolved in 2.6.3. #6684 <https://github.com/pypa/pipenv/issues/6684>_-r flag. #6689 <https://github.com/pypa/pipenv/issues/6689>_pipenv.utils.fileutils.is_valid_url. Import
is_valid_url from pipenv.utils.internet instead. pipenv's
stable API is the CLI; internal-only Python imports do not get
a deprecation window. Also removed the
pipenv.project.SourceNotFound re-export for the same reason —
import it from pipenv.utils.sources.pipenv check implementation will be
removed in v2027.0.0. Use pipenv audit or
pipenv check --scan during the transition. #6681 <https://github.com/pypa/pipenv/issues/6681>_Updated pip and cryptography dependencies to address security vulnerabilities
PIPENV_RESOLVER_TIMEOUT_S environment variable, making hung resolver processes recoverableDiagnostics.resolver_log with resolve records for improved debuggingpython_version = "3") in environment markersresolve_for_pipenv function, simplifying the resolver architectureResolverRequest/ResolverResponse schemas, improving protocol stability and error surfacingold_lock_data initialization)do_init so that ignore_pipfile/skip_lock flags are only pinned during initialization, not propagated to dependency installationSources.all to always return a listis_virtual_environment to tolerate virtual environment directories without a bin/Scripts subdirectorysys.path before importing the schema moduleresolved_default_deps as a dict rather than a list-r flag missing from README requirements.txt examplecheck command behaviors targeting the 2027 major release🔗 Full Changelog: v2026.6.2...v2026.7.0
cool-down-period in the [pipenv] section of the Pipfile.
Setting cool-down-period = "30d" instructs the resolver to only consider
package versions uploaded at least the specified number of days ago, via pip's
--uploaded-prior-to flag.pipenv install, pipenv lock, and pipenv sync. A hung mirror or
stuck pip download previously caused the resolver to block forever from
the user's perspective; the wait is now bounded by
PIPENV_RESOLVER_TIMEOUT_S (default 1800 seconds = 30 minutes,
chosen generously so normal resolutions are unaffected). On timeout the
subprocess is killed and a clear error is surfaced that names the
environment variable so users with legitimately large resolutions can
extend it.#T_F.3 <https://github.com/pypa/pipenv/issues/T_F.3>_[pipenv] resolver_timeout_seconds (Pipfile) >
PIPENV_RESOLVER_TIMEOUT_S (env var) > default (1800 seconds), and
is stamped onto RequestMetadata.deadline_seconds so the resolver
subprocess sees the same value the parent uses for
subprocess.wait(timeout=...). A hung resolver is now killed and a
structured error surfaced naming the override, instead of hanging
indefinitely. The in-process debug branch
(PIPENV_RESOLVER_PARENT_PYTHON=1) enforces the same deadline via
SIGALRM on Unix; Windows continues to rely on the subprocess
path for enforcement. #T_F.6 <https://github.com/pypa/pipenv/issues/T_F.6>_pipenv.utils.dependencies.pep423_name whose
scheme-token guard had an inverted predicate, making the branch that
preserves URL/VCS specifiers (e.g. git+ssh://host/path/some_repo)
from underscore-mangling unreachable. The predicate is now correct;
bare package names continue to be lowercased and have _ rewritten
to - as before. The sibling helper normalize_name in
pipenv.utils.requirements has been removed and its four callers
migrated to pep423_name.[[source]] URLs use
environment-variable placeholders. The GHSA-8xgg-v3jj-95m2 fix moved
credentials off pip's argv onto a merged netrc, but
write_credentials_netrc wrote our Pipfile-derived machine blocks
BEFORE the appended user netrc — and netrc.authenticators() returns
the LAST matching entry, so a stale system entry for the same host
silently overrode the freshly-expanded creds. Our blocks now come AFTER
the user's existing content. Additionally, the pylock.toml reader
now runs expand_url_credentials over its sources so users with
[pipenv] use_pylock = true see the same env-var expansion that
Pipfile.lock reads have always had. #6670 <https://github.com/pypa/pipenv/issues/6670>_pipenv update (no args) semantics of lock + sync.
Since 2026.0.0, pipenv update only re-resolved Pipfile entries whose
locked version no longer satisfied the Pipfile specifier, so relaxing a
pin (e.g. urllib3 = "<2.7.0" → urllib3 = "*") would not pick up
newer allowed releases — the lockfile silently stayed at the existing
pin. pipenv update now routes through do_lock when no packages
are given, re-resolving every Pipfile entry. The targeted
pipenv update <pkg> path is unchanged. #6672 <https://github.com/pypa/pipenv/issues/6672>_PIPENV_PYPI_MIRROR with embedded credentials (e.g.
https://user:pass@mirror.example.com). The GHSA-8xgg-v3jj-95m2 fix moved
credentials off pip's argv onto a temporary netrc, but the resolver's netrc
was written from the un-mirrored Pipfile sources, so the mirror's credentials
were dropped and resolution failed with 401 / ResolutionFailure. The
resolver netrc now applies the same PIPENV_PYPI_MIRROR substitution the
resolver subprocess uses, so the mirror credentials reach pip again. #6677 <https://github.com/pypa/pipenv/issues/6677>_python_version such as python_version = "3" in the Pipfile [requires] section, which the documentation lists as
valid. The version check added in 6535 compared the major and minor components
whenever fewer than three were given, but "3" parses to 3.0, so every
3.x interpreter but 3.0 was reported as a mismatch. That produced a spurious
warning on install and a fatal DeployException under --deploy. Only the
components actually given are compared now, so "3" matches any 3.x while
"3.13" and "3.13.1" keep their existing meaning. #6687 <https://github.com/pypa/pipenv/issues/6687>_cool-down-period locking to use package links from indexes that do
not expose upload-time metadata, while retaining the filter for indexes that do. #6691 <https://github.com/pypa/pipenv/issues/6691>_plette to 2.2.1.pip to 26.1.2 and refresh vendored libraries:
pipdeptree to 3.1.0, packaging to 26.2,
pythonfinder to 3.0.4, and tomlkit to 0.15.0.
Also harden is_within_directory() in patched pip to use
os.path.commonpath() instead of startswith, fixing a
containment check edge case for root directories and Windows
drive mismatches. #6680 <https://github.com/pypa/pipenv/issues/6680>_urllib3 in patched pip to 2.7.0 (fixes GHSA-qccp-gfcp-xxvc,
sensitive headers forwarded across origins in proxied low-level redirects).
Raise minimum virtualenv requirement from >=20.24.2 to >=20.26.6
(fixes GHSA-rqc4-2hc7-8c8v, command injection through activation scripts).
The three other urllib3 CVEs reported in this issue (GHSA-2xpw-w6gg-jr37,
GHSA-38jv-5279-wg99, GHSA-gm62-xv2j-4w53) were already resolved in 2.6.3. #6684 <https://github.com/pypa/pipenv/issues/6684>_-r flag. #6689 <https://github.com/pypa/pipenv/issues/6689>_pipenv.utils.fileutils.is_valid_url. Import
is_valid_url from pipenv.utils.internet instead. pipenv's
stable API is the CLI; internal-only Python imports do not get
a deprecation window. Also removed the
pipenv.project.SourceNotFound re-export for the same reason —
import it from pipenv.utils.sources.pipenv check implementation will be
removed in v2027.0.0. Use pipenv audit or
pipenv check --scan during the transition. #6681 <https://github.com/pypa/pipenv/issues/6681>_Support cool-down-period configuration in the [pipenv] section of the Pipfile
cool-down-period configuration in the [pipenv] section of the Pipfile.netrc; environment variables in pylock source URLs are now expanded correctlypipenv update with no packages specifiedplette vendor dependency to 2.2.1idna dependency in the pip group🔗 Full Changelog: v2026.6.1...v2026.6.2
cool-down-period in the [pipenv] section of the Pipfile.
Setting cool-down-period = "30d" instructs the resolver to only consider
package versions uploaded at least the specified number of days ago, via pip's
--uploaded-prior-to flag.[[source]] URLs use
environment-variable placeholders. The GHSA-8xgg-v3jj-95m2 fix moved
credentials off pip's argv onto a merged netrc, but
write_credentials_netrc wrote our Pipfile-derived machine blocks
BEFORE the appended user netrc — and netrc.authenticators() returns
the LAST matching entry, so a stale system entry for the same host
silently overrode the freshly-expanded creds. Our blocks now come AFTER
the user's existing content. Additionally, the pylock.toml reader
now runs expand_url_credentials over its sources so users with
[pipenv] use_pylock = true see the same env-var expansion that
Pipfile.lock reads have always had. #6670 <https://github.com/pypa/pipenv/issues/6670>_pipenv update (no args) semantics of lock + sync.
Since 2026.0.0, pipenv update only re-resolved Pipfile entries whose
locked version no longer satisfied the Pipfile specifier, so relaxing a
pin (e.g. urllib3 = "<2.7.0" → urllib3 = "*") would not pick up
newer allowed releases — the lockfile silently stayed at the existing
pin. pipenv update now routes through do_lock when no packages
are given, re-resolving every Pipfile entry. The targeted
pipenv update <pkg> path is unchanged. #6672 <https://github.com/pypa/pipenv/issues/6672>_plette to 2.2.1.Prevent mutation of cached parsed Pipfile data during dependency locking, resolving potential issues with corrupted lock state across operations
🔗 Full Changelog: v2026.6.0...v2026.6.1
pipenv install corrupting existing inline-table or outline-table
Pipfile entries (six = {version = "*"}, [packages.requests]). The
locker was popping version/ref keys directly off the cached
parsed_pipfile document, so subsequent writes emitted
six = {} and dropped the version specifier from sibling packages. #6657 <https://github.com/pypa/pipenv/issues/6657>_Strip credentials from pip argument vectors to prevent credential exposure in logs and process listings (GHSA-8xgg-v3jj-95m2)
data_filter fallback to prevent path traversal during package installation (GHSA-p4qx-p8p6-4gjf)git+ssh package sources in PipfilePIPENV_PROJECT_DIR not being expanded correctly in Pipfile script definitionspipenv shell breaking terminal input echo after exittarget_marker_version helper alias for backwards compatibility_target_marker_environment returning incorrect value when allow_global=Truepygments from 2.19.2 to 2.20.0pytest (development dependency)🔗 Full Changelog: v2026.5.2...v2026.6.0
pipenv shell breaking terminal input echo on Linux. The previous
implementation toggled setecho(True/False) on the spawned child around
its internal setup commands, which fought with the shell's own readline
termios management — producing permanently-disabled echo (GH-6572) or
double-echoed keystrokes (1234 → 11223344). fork_compat no
longer touches pty termios; instead it drains the synchronisation sentinel
from the pexpect buffer twice (once for the echoed command, once for its
output) so nothing leaks into interact(). #6633 <https://github.com/pypa/pipenv/issues/6633>_pipenv run <command> -h <arg> now passes -h through to the command
instead of showing pipenv's help. All arguments following run_command are
captured verbatim via argparse REMAINDER, so flags like -h that pipenv
itself also defines no longer collide with the wrapped command. #6641 <https://github.com/pypa/pipenv/issues/6641>_ValueError: invalid literal for int() with base 10 when the Pipfile's
[requires] section uses a PEP 440 specifier (e.g. python_version = ">=3.9").
Specifier values no longer produce a Python-version override; the running
interpreter's actual version is used for marker evaluation instead. #6645 <https://github.com/pypa/pipenv/issues/6645>_Ignoring …: markers … don't match your environment warnings (and the corresponding
missing installs) when pipenv sync --python X.Y is driven by a
different system Python. #6647 <https://github.com/pypa/pipenv/issues/6647>_pipenv run now expands $PIPENV_PROJECT_DIR and other Pipenv-managed
environment variables inside Pipfile script arguments before direct command
execution, so project-relative script paths resolve correctly. #6652 <https://github.com/pypa/pipenv/issues/6652>_#6651 <https://github.com/pypa/pipenv/issues/6651>_Fixed pipenv audit --locked failing when used with Pipfile.lock and the legacy shell completion environment variable
pipenv audit --locked failing when used with Pipfile.lock and the legacy shell completion environment variableargcomplete instead of the legacy implementation🔗 Full Changelog: v2026.5.1...v2026.5.2
Resolved CLI regressions introduced by the argparse migration, including broken command-line options and argument handling
fork_compat history test on Windows where pexpect.spawn is unavailable, improving cross-platform test reliabilitypygments dependency from 2.19.2 to 2.20.0 in examples🔗 Full Changelog: v2026.5.0...v2026.5.1
Add "Did You Mean" suggestions for mistyped subcommands, helping users quickly identify and correct typos in CLI commands
click and click_didyoumean, reducing bundled dependencies in favor of external packagesimportlib-metadata and zipp following Python 3.9 end-of-lifecached_property Python 3.7 compatibility fallbackdependency_groups markers before passing dependencies to pip during locking, preventing resolution errorsdependency_groups markers from being written on pylock re-generationPipenvException calls super().__init__() so str(exc) returns the properly formatted message🔗 Full Changelog: v2026.4.0...v2026.5.0
Add optional shell completion via argcomplete. Install with
pip install "pipenv[completion]" and activate once with
eval "$(register-python-argcomplete pipenv)".
Mistyped subcommand names now produce "Did you mean …?" suggestions using
difflib, replacing the click_didyoumean vendor library. #6619 <https://github.com/pypa/pipenv/issues/6619>_
pylock.toml re-generation duplicating dependency_groups markers
for develop packages. Each run of pipenv pylock --generate (or any
command that rewrites the lock file) prepended the dependency_groups
prefix even when it was already present, producing malformed markers like
('dev' in dependency_groups) and (('dev' in dependency_groups) and ...).
This caused pipenv install to crash with a KeyError: 'dependency_groups'
when evaluating environment markers. #6621 <https://github.com/pypa/pipenv/issues/6621>_colorama. Rich's Console supersedes colorama's Windows
ANSI escape code handling, and this was the last remaining usage in Pipenv. #6621 <https://github.com/pypa/pipenv/issues/6621>_click and click_didyoumean libraries. The CLI has
been rewritten to use Python's standard-library argparse, eliminating
Pipenv's dependency on Click entirely. #6619 <https://github.com/pypa/pipenv/issues/6619>_importlib-metadata and zipp libraries. Python 3.9
is end-of-life and Pipenv requires Python 3.10+, where importlib.metadata
is available in the standard library. #6622 <https://github.com/pypa/pipenv/issues/6622>_ruff-format in pre-commit,
remove redundant standalone Ruff job, and add a tests-smoke gate that
runs Python 3.12 across all OSes before the full version matrix — cutting
wasted compute on version-agnostic failures.
Disable Windows Defender real-time scanning for Python toolcache,
workspace, virtualenvs, and pip cache on Windows runners
to reduce I/O overhead.--extras CLI option : Specify optional dependency categories directly from the command line
--extras CLI option: Specify optional dependency categories directly from the command line--exclude-index flag for requirements command: Exclude index URLs from generated requirements outputPIPENV_PYENV_ONLY environment variable: Restrict Python discovery exclusively to pyenv, ignoring other Python installationsPIPENV_KEYRING_PROVIDER environment variable: Enable Windows Credential Manager and other keyring backends for private index authenticationpython_version: Pipfile now accepts full PEP 440 specifiers (e.g., >=3.10) for Python version constraints[build-system] requires support in Pipfile: Define build system requirements directly in Pipfilepipenv sync from pylock.toml: Sync environments using pylock.toml without requiring Pipfile.lockpipenv sync and install --ignore-pipfile now work without a Pipfile present--system flag support improved across multiple commands--all flag for update and upgrade commands fixed to correctly target all packagesproper_case lookup timeout increased from 0.3s to 3s to reduce failures on slow networksPIPENV_VERSION environment variable is now ignored when running --version flagpipenv run argumentspipenv shell now correctly launches bash or PowerShell instead of defaulting to cmdpipenv shell now properly suspends with Ctrl+Z (job control restored)pipenv shell activates correctly even when shell startup scripts produce interactive outputsys_platform shorthand markers: Short-form platform markers are now correctly included in pip requirement linespython_full_version in marker evaluation, including major-only python_version valuespython_full_version specifiers when using the Windows py launcherfile:// URL dependencies: File-scheme dependencies are now correctly recorded during lockingpython_version mismatch with venv: Records the correct Python version when the venv Python and PATH Python disagreedistutils missing fallback: Falls back to sysconfig when distutils is unavailable (Python 3.12+)pip.conf extra-index hash collection: Hashes from pip.conf extra-index URLs are now collected during lockingpip.conf index suppression at install time: Prevents hash mismatch errors caused by pip.conf injecting extra indexes during installindex_lookup is now populated from all Pipfile sections when locking non-default categories--where exit code: Fixed incorrect exit code for the --where flag_create_builtin_venv_cmd: No longer incorrectly prepends a drive letter to Unix paths when run on Windowsvenv when virtualenv fails for non-standard interpretersResolutionTooDeepError: Fixed excessive recursion caused by incorrect marker evaluation during resolutionfix --where exit code: Corrected exit behavior for the requirements --where option🔗 Full Changelog: v2026.2.2...v2026.4.0
Deprecate the --rm option in favor of the new pipenv remove command
pipenv remove command as a dedicated subcommand for removing virtualenvs--rm option in favor of the new pipenv remove command--pre flag behavior with pip 26+ by calling check_release_control_exclusive in Resolver.pip_options_clean_unused_dependencies to prevent errors during upgrade cleanup (#6002)python -m virtualenv from an empty directory to prevent PYTHONPATH pollution affecting virtual environment creation (#6568)🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.2.1...v2026.2.2
pipenv upgrade now correctly removes transitive dependencies that are no longer needed after a package is upgraded (e.g. pytz is removed when upgrading Django from 3.2.x to 4.2+). A safety guard was also added to _clean_unused_dependencies to prevent incorrectly wiping all packages when a full resolution returns an empty result due to a subprocess failure. #6002 <https://github.com/pypa/pipenv/issues/6002>_#6569 <https://github.com/pypa/pipenv/issues/6569>_#6564 <https://github.com/pypa/pipenv/issues/6564>_Always restore PTY echo state via try/finally in fork_compat, ensuring terminal echo is reliably re-enabled even if an error occurs during subprocess
try/finally in fork_compat, ensuring terminal echo is reliably re-enabled even if an error occurs during subprocess execution🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.2.0...v2026.2.1
Support sequential script execution via TOML array syntax in [scripts] section
[scripts] section--all flag to install and sync commands to install all Pipfile categoriesPIPENV_DEFAULT_CATEGORIES environment variable for configuring default package categoriesvenv_in_project to be set in the [pipenv] section of Pipfilepipenv runpymanager) on Windowsextra-index-url and fix trusted-host handling in pip.conf--no-binary option not being stored in Pipfile--dry-run help text for the update commandupdatepipenv --rm removing the wrong virtualenv when .venv directory coexists with WORKON_HOME venv--python version differs from the existing virtual environmentinstall -r to match sync behaviorPermissionError on Windows when scanning restricted PATH entriesfile:// URL in Pipfile and fix local editable path/file key handlinguninstall --all no longer wiping Pipfile.lockpath key for local dependencies and file key for remote URLs in Pipfile entries.exe path recognition in pipenv activate on Windowsfork_compatshlex compatibilitypythonfinder vendored dependency to version 3.0.2platform_machine examplesblack from 24.3.0 to 26.3.1🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.1.0...v2026.2.0
Fixed regression in handling of packaging version strings with prereleases
SearchScope dataclass to use slots=True parameter, resolving __slots__ conflict with default values🔗 Full Changelog: https://github.com/pypa/pipenv/compare/v2026.0.3...v2026.1.0
Fix pipenv shell --quiet to actually suppress output by @matteius in https://github.com/pypa/pipenv/pull/6500
Full Changelog: https://github.com/pypa/pipenv/compare/v2026.0.2...v2026.0.3
Fix: Allow shell builtins to work with pipenv run by @matteius in https://github.com/pypa/pipenv/pull/6487
Full Changelog: https://github.com/pypa/pipenv/compare/v2026.0.1...v2026.0.2
Fix pip.conf index-url not being honored after pip 25.3 update by @matteius in https://github.com/pypa/pipenv/pull/6479
Full Changelog: https://github.com/pypa/pipenv/compare/v2026.0.0...v2026.0.1
index-url from pip configuration files (/etc/pip.conf, ~/.pip/pip.conf, etc.) which was broken after vendoring pip 25.3 due to a change in pip's Configuration.items() return format. #6478 <https://github.com/pypa/pipenv/issues/6478>_Add pipenv audit command using pip-audit for vulnerability scanning by @matteius in https://github.com/pypa/pipenv/pull/6457
Full Changelog: https://github.com/pypa/pipenv/compare/v2025.1.3...v2026.0.0
Add --system flag to pipenv run command. This allows running scripts
defined in Pipfile's [scripts] section without creating a virtualenv,
which is useful in Docker environments where packages are installed with
pipenv install --system. #2692 <https://github.com/pypa/pipenv/issues/2692>_
Allow pipenv install --system <package> to install specific packages to the
system Python. Previously this was blocked with an error message. This enables
Docker workflows where users want to interactively add packages to a project
that uses system-level installation. #4086 <https://github.com/pypa/pipenv/issues/4086>_
Added support for PEP 751 pylock.toml files:
use_pylock = true to the [pipenv] section of your Pipfile to generate pylock.toml files alongside Pipfile.lock.pylock_name = "name" in the [pipenv] section to generate named pylock files (e.g., pylock.name.toml). #6391 <https://github.com/pypa/pipenv/issues/6391>_Add support for --dev flag in pipenv uninstall command to remove packages from dev-packages section directly. #6392 <https://github.com/pypa/pipenv/issues/6392>_
Add PIPENV_PYENV_AUTO_INSTALL environment variable to automatically install missing Python versions via pyenv or asdf without prompting the user. #6408 <https://github.com/pypa/pipenv/issues/6408>_
Fix --system and --python flags to work together correctly. Previously,
using both flags would still create a virtualenv. Now when --system is used
with --python, pipenv validates that the specified Python version exists
on the system and raises a clear error if not found. #4973 <https://github.com/pypa/pipenv/issues/4973>_
Make --quiet flag actually suppress output during pipenv install and pipenv sync.
Previously, messages like "Installing dependencies from Pipfile.lock" and "All dependencies are now up-to-date!" were shown even with --quiet. #5037 <https://github.com/pypa/pipenv/issues/5037>_
Fix SSH git username being incorrectly redacted to **** when importing
from requirements.txt, which caused lockfile generation to fail. #5599 <https://github.com/pypa/pipenv/issues/5599>_
Fix malformed Pipfile.lock causing command to exit successfully with code 0.
Now raises LockfileCorruptException which properly propagates as an error. #5622 <https://github.com/pypa/pipenv/issues/5622>_
Fix VCS dependencies (git, etc.) not being reinstalled when the ref/commit changes in the lockfile.
Previously, pipenv update would update the lockfile with the new commit hash but the installed
package in the virtualenv would remain unchanged, requiring pipenv --rm to force a reinstall. #5791 <https://github.com/pypa/pipenv/issues/5791>_
Fix pipenv-resolver CLI not working. The command now properly handles
package arguments from the command line, sets a default category of "default",
and correctly loads the pipenv module with all submodules. #5862 <https://github.com/pypa/pipenv/issues/5862>_
Fix --lock-only flag for pipenv upgrade command to properly skip adding package specifiers to Pipfile when set. #6131 <https://github.com/pypa/pipenv/issues/6131>_
Improve error handling in do_lock by properly catching and handling exceptions from venv_resolve_deps.
RuntimeError now exits cleanly, and other exceptions display a full traceback for debugging. #6166 <https://github.com/pypa/pipenv/issues/6166>_
Fixed pipenv install --index=xxx where xxx is not a valid URL or known index name now raises a clear error instead of creating a malformed source entry in the Pipfile. #6168 <https://github.com/pypa/pipenv/issues/6168>_
Fix PIPENV_ACTIVE environment variable not being unset when running deactivate in a pipenv shell, which caused "Shell for UNKNOWN_VIRTUAL_ENVIRONMENT already activated" errors on subsequent pipenv shell commands. #6220 <https://github.com/pypa/pipenv/issues/6220>_
Fix pipenv lock to properly apply default package version constraints when resolving dev-packages and other categories. When a package is constrained in the [packages] section (e.g., httpx = "==0.24.1"), dev-packages that depend on it will now be constrained to compatible versions. #6347 <https://github.com/pypa/pipenv/issues/6347>_
Fix typo in get_constraints_from_deps where version string was incorrectly formatted using the entire dependency dict instead of the version string. #6354 <https://github.com/pypa/pipenv/issues/6354>_
Fix for PEP660 editable VCS dependencies not reinstalled correctly. #6362 <https://github.com/pypa/pipenv/issues/6362>_
Resolver errors now display clean, user-friendly messages instead of confusing stacktraces in non-verbose mode. #6388 <https://github.com/pypa/pipenv/issues/6388>_
Validate Python version when using --system flag.
Previously, pipenv install --system --deploy would silently proceed even if the system Python version didn't match the python_version specified in Pipfile/Pipfile.lock.
Now it properly raises a DeployException when the versions don't match. #6403 <https://github.com/pypa/pipenv/issues/6403>_
Fix editable package name being incorrectly parsed from test files in subdirectories.
Previously, when installing an editable local package, pipenv would recursively search
all subdirectories for setup.py files. This could cause a test file with a
setup(name='foo') call to be incorrectly used as the package name. Now, setup.py,
setup.cfg, and pyproject.toml are only checked in the root directory. Metadata
files (PKG-INFO, METADATA) are still searched in .egg-info and .dist-info
directories.
Fixes #6409 #6409 <https://github.com/pypa/pipenv/issues/6409>_
Fix pipenv check --quiet not working properly. The --quiet flag now
correctly suppresses informational output and forces JSON output format for
safety so that results can be parsed correctly.
Fixes #6414 #6414 <https://github.com/pypa/pipenv/issues/6414>_
Fix pipenv update --dev (and pipenv update --categories develop) updating
transitive dependencies in the develop section independently from the default
section. Now, any packages that appear in both default and develop will use
the version from default, ensuring consistent dependency versions between
production and development environments.
Fixes #6420 #6420 <https://github.com/pypa/pipenv/issues/6420>_
Fix markers not being respected for file-based and VCS dependencies during resolution.
Markers are now correctly included in the pip install line, allowing pipenv to skip
resolution for dependencies whose markers don't match the current environment. #6431 <https://github.com/pypa/pipenv/issues/6431>_
Fix pipenv requirements --dev-only --from-pipfile to only include packages explicitly listed in dev-packages, not packages from other categories that happen to also be transitive dependencies of dev packages. #6440 <https://github.com/pypa/pipenv/issues/6440>_
Fix pipenv update incorrectly marking all packages as modified when Pipfile contains version ranges (e.g., >=2.25.1) instead of exact versions. The comparison now properly checks if the locked version satisfies the Pipfile specifier, rather than doing a string comparison. This significantly improves performance of pipenv update when no packages have actually been modified. #6454 <https://github.com/pypa/pipenv/issues/6454>_
Fix TypeError: cannot unpack non-iterable PermissionError object on Windows with Python 3.12+
when removing read-only files (e.g., git pack files). The handle_remove_readonly error handler
now properly handles both the deprecated onerror callback signature (tuple) and the new
onexc callback signature (exception instance) introduced in Python 3.12. #6474 <https://github.com/pypa/pipenv/issues/6474>_
Fix benchmark CI job hanging by adding timeout and PIPENV_YES=1 environment variable to prevent interactive prompts. #6477 <https://github.com/pypa/pipenv/issues/6477>_
Fix subprocess deadlock in resolver that could cause pipenv lock to hang indefinitely when the resolver subprocess writes large amounts of data to stdout. The fix reads stdout and stderr concurrently using threads, preventing pipe buffer deadlocks. #benchmark <https://github.com/pypa/pipenv/issues/benchmark>_
pipenv scan as a standalone command. The correct usage is pipenv check --scan. #6396 <https://github.com/pypa/pipenv/issues/6396>_Fix Python3.10/3.11 tomli compatibility by @matteius in https://github.com/pypa/pipenv/pull/6449
Full Changelog: https://github.com/pypa/pipenv/compare/v2025.1.1...v2025.1.3
from __future__ import annotations to files in
pipenv/patched/pip that use Python 3.10+ type annotation syntax. #6448 <https://github.com/pypa/pipenv/issues/6448>_Swap pip-args with extra-pip-args by @agalazis in https://github.com/pypa/pipenv/pull/6441
Full Changelog: https://github.com/pypa/pipenv/compare/v2025.0.4...v2025.1.0
Fix editable installation from relative paths on Windows by @stewartmiles in https://github.com/pypa/pipenv/pull/6416
Full Changelog: https://github.com/pypa/pipenv/compare/v2025.0.3...v2025.0.4
#6419 <https://github.com/pypa/pipenv/issues/6419>_#6425 <https://github.com/pypa/pipenv/issues/6425>_#6426 <https://github.com/pypa/pipenv/issues/6426>_Fix release notes generation by @matteius in https://github.com/pypa/pipenv/pull/6399
--welcome). by @stewartmiles in https://github.com/pypa/pipenv/pull/6410Full Changelog: https://github.com/pypa/pipenv/compare/v2025.0.2...v2025.0.3
pip==25.1.1 latest. #6400 <https://github.com/pypa/pipenv/issues/6400>_Cleanup unused dependencies by @matteius in https://github.com/pypa/pipenv/pull/6386
Full Changelog: https://github.com/pypa/pipenv/compare/v2025.0.1...v2025.0.2
#6386 <https://github.com/pypa/pipenv/issues/6386>_UnboundLocalError in ensure_python when SESSION_IS_INTERACTIVE=False, using pyenv, and python version in Pipfile not available. #6389 <https://github.com/pypa/pipenv/issues/6389>_HOTFIX import requirements by @matteius in https://github.com/pypa/pipenv/pull/6385
Full Changelog: https://github.com/pypa/pipenv/compare/v2025.0.0...v2025.0.1
2025.0.0 #6385 <https://github.com/pypa/pipenv/issues/6385>_Deprecation Notice: Make safety an optional dependency via extras by @matteius in https://github.com/pypa/pipenv/pull/6365
bin/ / Scripts/ path resolution using sysconfig mechanism by @ByteB4rb1e in https://github.com/pypa/pipenv/pull/6373Full Changelog: https://github.com/pypa/pipenv/compare/v2024.4.1...v2025.0.0
This PR completely refactors the pythonfinder module to improve efficiency, reduce logical errors, and fix support for PEP 514 (Python registration in the Windows registry). The refactoring replaces the complex object hierarchy with a more modular, composition-based approach that is easier to maintain and extend.
The original pythonfinder implementation had several issues:
PythonInfo dataclassThe refactored implementation continues to support all required features:
#6360 <https://github.com/pypa/pipenv/issues/6360>_Almost finished with conversion off click echo/secho to rich console outputs. #6366 <https://github.com/pypa/pipenv/issues/6366>_
Make safety an optional dependency via extras
#safety-extras <https://github.com/pypa/pipenv/issues/safety-extras>_Fix launching PowerShell on UNC paths #6322 <https://github.com/pypa/pipenv/issues/6322>_
Check if we need to upgrade a package in more than one category. #6361 <https://github.com/pypa/pipenv/issues/6361>_
Fix issue with default constraints not applying to other package categories. #6364 <https://github.com/pypa/pipenv/issues/6364>_
Fix for parsing and using the star specifier in install and update/upgrade commands. #6378 <https://github.com/pypa/pipenv/issues/6378>_
Fixed KeyError when installing packages with invalid Python version specifiers in their metadata. #6380 <https://github.com/pypa/pipenv/issues/6380>_
Fixed an issue with installing local packages that have spaces in their path names. #6381 <https://github.com/pypa/pipenv/issues/6381>_
This PR refactors the logic for determining virtual environment script paths
by leveraging sysconfig's built-in mechanisms. By removing
platform-dependent logic, pipenv now offers enhanced compatibility with
POSIX-like environments, including Cygwin and MinGW. The fix also mitigates
execution inconsistencies in non-native Windows environments, improving
portability across platforms.
The original logic for determining the scripts path was unable to handle the
deviations of MSYS2 MinGW CPython identifying as nt platform, yet using a
POSIX {base}/bin path, instead of {base}/Scripts.
Removed custom logic for determining virtualenv scripts path in favor of
retrieving the basename of the path string returned by
``sysconfig.get_path('scripts')```. #6737 <https://github.com/pypa/pipenv/issues/6737>_
check command to support the new scan functionalityThe check command has been deprecated and will be unsupported beyond June 1, 2025.
Instead of adding a separate scan command, we've updated the check command to include a --scan option.
Key changes:
--scan option to the check command to use the new scan functionalitycheck will run the scan command by defaulttempfile module to ensure proper cleanupUsers are encouraged to start using the --scan option with the check command to prepare for the future change.
This option requires users to obtain and configure an API key from https://pyup.io. #safety-command <https://github.com/pypa/pipenv/issues/safety-command>_
Running "pipenv shell" on MacOS in Powershell (pwsh) references incorrect Activate.ps1 _
Version v2024.4.1
@aidencullo @oz123 @samer-shah @shdarrina @shaneikennedy @socram8888
correct regression in --skip-lock by @matteius in https://github.com/pypa/pipenv/pull/6304
Full Changelog: https://github.com/pypa/pipenv/compare/v2024.3.1...v2024.4.0
#6318 <https://github.com/pypa/pipenv/issues/6318>_#6321 <https://github.com/pypa/pipenv/issues/6321>_#6327 <https://github.com/pypa/pipenv/issues/6327>_#6329 <https://github.com/pypa/pipenv/issues/6329>_#6216 <https://github.com/pypa/pipenv/issues/6216>_try rebuilding the docs by @matteius in https://github.com/pypa/pipenv/pull/6291
Full Changelog: https://github.com/pypa/pipenv/compare/v2024.3.0...v2024.3.1
#6291 <https://github.com/pypa/pipenv/issues/6291>_2024.3.0 when using the --system flag without --deploy flag. #6295 <https://github.com/pypa/pipenv/issues/6295>_pipenv update routine to allow for package upgrades without requiring an existing lockfile. This change improves the flexibility of the update process by determining which packages require updating and handling cases where the lockfile is absent or partially defined.#6299 <https://github.com/pypa/pipenv/issues/6299>_Solve upgrade can create incompatible dependency versions in lock file + other bugs by @matteius in https://github.com/pypa/pipenv/pull/6282
Full Changelog: https://github.com/pypa/pipenv/compare/v2024.2.0...v2024.3.0
Fix dependency resolution edge cases and versioning constraints handling:
--reverse dependency graph output matching pipdeptree~= and other version specifiers during updatesKey Changes:
This improves stability when working with complex dependency trees and version constraints. #6281 <https://github.com/pypa/pipenv/issues/6281>_
Fixes issue with --skip-lock not providing pip the proper package specifier when version was a string (issue did not impact dict with version key). #6288 <https://github.com/pypa/pipenv/issues/6288>_
Bump black from 23.3 to 24.3.0 by @dependabot in https://github.com/pypa/pipenv/pull/6112
Full Changelog: https://github.com/pypa/pipenv/compare/v2024.1.0...v2024.2.0
Refactored and simplified install routines, improving maintainability and reliability (#6276)
Enhanced VCS URL handling with better environment variable support (#6276)
#6276 <https://github.com/pypa/pipenv/issues/6276>_#6275 <https://github.com/pypa/pipenv/issues/6275>_Vendor in Pip 24.1.2 by @matteius in https://github.com/pypa/pipenv/pull/6253
Full Changelog: https://github.com/pypa/pipenv/compare/v2024.0.3...v2024.1.0
pip==24.0 to pip==24.1.2. #6253 <https://github.com/pypa/pipenv/issues/6253>_#6256 <https://github.com/pypa/pipenv/issues/6256>_Fix logging error by @yosufali in https://github.com/pypa/pipenv/pull/6246
Full Changelog: https://github.com/pypa/pipenv/compare/v2024.0.2...v2024.0.3
ResourceWarning warning for temporary files that are cleaned on program exit. #6151 <https://github.com/pypa/pipenv/issues/6151>_#6171 <https://github.com/pypa/pipenv/issues/6171>_pipenv uninstall --all failing when the virtual environment no longer exists. #6185 <https://github.com/pypa/pipenv/issues/6185>_#6242 <https://github.com/pypa/pipenv/issues/6242>_packaging>=22 on some systems by setting it as a dependency. #6243 <https://github.com/pypa/pipenv/issues/6243>_PiPenv -> Pipenv by @gtback in https://github.com/pypa/pipenv/pull/6184
pipenv update --outdated output by @BarrensZeppelin in https://github.com/pypa/pipenv/pull/6179pipenv install --skip-lock by @matteius in https://github.com/pypa/pipenv/pull/6225Full Changelog: https://github.com/pypa/pipenv/compare/v2024.0.1...v2024.0.2
#6240 <https://github.com/pypa/pipenv/issues/6240>_#6177 <https://github.com/pypa/pipenv/issues/6177>_#6179 <https://github.com/pypa/pipenv/issues/6179>_#6197 <https://github.com/pypa/pipenv/issues/6197>_#6202 <https://github.com/pypa/pipenv/issues/6202>_#6207 <https://github.com/pypa/pipenv/issues/6207>_--all should not clear the Pipfile entries. #6209 <https://github.com/pypa/pipenv/issues/6209>_#6222 <https://github.com/pypa/pipenv/issues/6222>_pipenv install --skip-lock after behavioral install refactor introduced regression. No Pipfile.lock is generated with this fix and installation of vcs no longer fails with revision missing error. #6225 <https://github.com/pypa/pipenv/issues/6225>_#6240 <https://github.com/pypa/pipenv/issues/6240>_#6178 <https://github.com/pypa/pipenv/issues/6178>_#6182 <https://github.com/pypa/pipenv/issues/6182>_#6216 <https://github.com/pypa/pipenv/issues/6216>_#6235 <https://github.com/pypa/pipenv/issues/6235>_Update plette to version 2.1.0 by @oz123 in https://github.com/pypa/pipenv/pull/6174
Full Changelog: https://github.com/pypa/pipenv/compare/v2024.0.0...v2024.0.1
Update CONTRIBUTING.md by @PzaThief in https://github.com/pypa/pipenv/pull/6084
scripts section and other small changes by @sss-ng in https://github.com/pypa/pipenv/pull/6152pipenv requirements by @sanspareilsmyn in https://github.com/pypa/pipenv/pull/6156Full Changelog: https://github.com/pypa/pipenv/compare/v2023.12.1...v2024.0.0
--extra-pip-args also in the resolver steps. #6006 <https://github.com/pypa/pipenv/issues/6006>_uninstall command now does the inverse of upgrade which means it no longer invokes a full lock cycle which was problematic for projects with many dependencies. #6029 <https://github.com/pypa/pipenv/issues/6029>_pipenv requirements subcommand now supports the --from-pipfile flag. When this flag is used, the requirements file will only include the packages explicitly listed in the Pipfile, excluding any sub-packages. #6156 <https://github.com/pypa/pipenv/issues/6156>_pipenv==2024.0.0 denotes the first major release of our semver strategy.
As much requested, the install no longer does a complete lock operation. Instead install follows the same code path as pipenv update (which is upgrade + sync).
This is what most new users expect the behavior to be; it is a behavioral change, a necessary one to make the tool more usable.
Remember that complete lock resolution can be invoked with pipenv lock just as before. #6098 <https://github.com/pypa/pipenv/issues/6098>_#6126 <https://github.com/pypa/pipenv/issues/6126>_#6136 <https://github.com/pypa/pipenv/issues/6136>_pipenv converts off pkg_resources API usages. This necessitated also vendoring in:
pipdeptree==2.18.1 which also converted off pkg_resourcesimportlib-metadata==7.1.0 to continue supporting python 3.8 and 3.9packaging==24.0 since the packaging we were utilizing in pip's vendor was insufficient for this conversion. #6139 <https://github.com/pypa/pipenv/issues/6139>#6164 <https://github.com/pypa/pipenv/issues/6164>_pip==24.0 #6117 <https://github.com/pypa/pipenv/issues/6117>_click-didyoumean==0.3.1expect==4.9.0pipdeptree==2.16.2python-dotenv==1.0.1ruamel.yaml==0.18.6shellingham==1.5.4tomlkit==0.12.4 #6118 <https://github.com/pypa/pipenv/issues/6118>_Issue-6079 Remove debug print statements that mistakenly got released by @matteius in https://github.com/pypa/pipenv/pull/6082
Full Changelog: https://github.com/pypa/pipenv/compare/v2023.12.0...v2023.12.1
#6079 <https://github.com/pypa/pipenv/issues/6079>_NOTE: this is our second semver release with a plan to release major version 3000 later this winter/Spring.
Full Changelog: https://github.com/pypa/pipenv/compare/v2023.11.17...v2023.12.0
#6065 <https://github.com/pypa/pipenv/issues/6065>_#6069 <https://github.com/pypa/pipenv/issues/6069>_CI variable to use do_run_nt shell logic, as the original reasons for that patch were no longer valid. #6072 <https://github.com/pypa/pipenv/issues/6072>_Chore: Resolve CI deprecation warnings by @stumpylog in https://github.com/pypa/pipenv/pull/6025
project.get_default_index() populate a default name by @deivid-rodriguez in https://github.com/pypa/pipenv/pull/6021Full Changelog: https://github.com/pypa/pipenv/compare/v2023.11.15...v2023.11.17
#6008 <https://github.com/pypa/pipenv/issues/6008>_#6021 <https://github.com/pypa/pipenv/issues/6021>_#6056 <https://github.com/pypa/pipenv/issues/6056>_0.12.3 #6024 <https://github.com/pypa/pipenv/issues/6024>_#6055 <https://github.com/pypa/pipenv/issues/6055>_Treat all return paths of this method as strings by @matteius in https://github.com/pypa/pipenv/pull/6017
Full Changelog: https://github.com/pypa/pipenv/compare/v2023.11.14...v2023.11.15
2023.11.14 #6017 <https://github.com/pypa/pipenv/issues/6017>_Restore this code that should prevent the string has no attribute update bug. by @matteius in https://github.com/pypa/pipenv/pull/6007
Full Changelog: https://github.com/pypa/pipenv/compare/v2023.10.24...v2023.11.14
PIPENV_VENV_IN_PROJECT is false. #6009 <https://github.com/pypa/pipenv/issues/6009>_#5936 <https://github.com/pypa/pipenv/issues/5936>_#5994 <https://github.com/pypa/pipenv/issues/5994>_#6011 <https://github.com/pypa/pipenv/issues/6011>_Simplify sorting code by @daveschaefer in https://github.com/pypa/pipenv/pull/5990
Full Changelog: https://github.com/pypa/pipenv/compare/v2023.10.20...v2023.10.24
#5987 <https://github.com/pypa/pipenv/issues/5987>_#5988 <https://github.com/pypa/pipenv/issues/5988>#5986 <https://github.com/pypa/pipenv/issues/5986>_23.3.1 #5991 <https://github.com/pypa/pipenv/issues/5991>_Drop pep517 by @oz123 in https://github.com/pypa/pipenv/pull/5970
--py to use print instead of console.print by @notEvil in https://github.com/pypa/pipenv/pull/5971Full Changelog: https://github.com/pypa/pipenv/compare/v2023.10.3...v2023.10.20
#5966 <https://github.com/pypa/pipenv/issues/5966>_#5979 <https://github.com/pypa/pipenv/issues/5979>_--py to use print preventing insertion of newline characters #5969 <https://github.com/pypa/pipenv/issues/5969>_#5970 <https://github.com/pypa/pipenv/issues/5970>_#5879 <https://github.com/pypa/pipenv/issues/5879>_Include the package name in the information to the resolver by @matteius in https://github.com/pypa/pipenv/pull/5930
Full Changelog: https://github.com/pypa/pipenv/compare/v2023.9.8...v2023.10.3
#5934 <https://github.com/pypa/pipenv/issues/5934>_#5941 <https://github.com/pypa/pipenv/issues/5941>_ignore_compatibility was supposed to default to False by @matteius in https://github.com/pypa/pipenv/pull/5926
Full Changelog: https://github.com/pypa/pipenv/compare/v2023.9.7...v2023.9.8
#5926 <https://github.com/pypa/pipenv/issues/5926>_Update build to use exclusively pyproject.toml by @kalebmckale in https://github.com/pypa/pipenv/pull/5836
Full Changelog: https://github.com/pypa/pipenv/compare/v2023.9.1...v2023.9.7
pyproject.tomlModernizes the build process by consolidating all of setuptools metadata within pyproject.toml and removing deprecated setup.cfg and setup.py. #5837 <https://github.com/pypa/pipenv/issues/5837>_
#5887 <https://github.com/pypa/pipenv/issues/5887>_#5905 <https://github.com/pypa/pipenv/issues/5905>_#5919 <https://github.com/pypa/pipenv/issues/5919>_--skip-lock. #5920 <https://github.com/pypa/pipenv/issues/5920>_#5921 <https://github.com/pypa/pipenv/issues/5921>_ssh:// vcs URLs introduced in 2023.8.21 whereby ssh vcs URLs are expected to have at least one @ symbol. #58462023.8.19 #5841version command. #5838--categories option now works with requirements.txt file. #5722--skip-lock flag which was deprecated, has now been removed to unblock modernizing the pipenv resolver code. #5805pip==23.2 which includes everything from the pip changelog. Drops the "install_compatatability_finder" pip internals patch. #5808PIPENV_RESOLVER_PARENT_PYTHON environment variable to 1 (useful for internal debugging). #5809pythonfinder==2.0.5. #58122023.7.11 (2023-07-11)
requirements command related to standard index extras and handling of local file requirements. #5784--system flag usage. #5773_get_requests_session method to consider PIP_CLIENT_CERT value when present. #5746requirements command that was causing package installs after upgrade to requirementslib==3.0.0. #5755error: invalid command 'egg_info' edge case with requirementslib 3.0.0. It exposed pipenv resolver sometimes was using a different python than expected. #5760pipenv. #5737--skip-lock flag as it bypasses the security benefits of pipenv. Plus it lacks proper deterministic support of installation from multiple package indexes. #5737sys.path modifications and as a result fixes keyring support. #5719pipdeptree==2.8.0 which fixes edge cases of the pipenv graph command. #5720pythonfinder==2.0.4 with fix for "RecursionError: maximum recursion depth exceeded". #5709--index argument in update and upgrade commands. #5692pythonfinder==2.0.0 which also brings in pydantic==1.10.7. #5677pip==23.1.2 latest. #5671requirementslib==2.3.0 which drops usage of vistir. #5672Checks environment variable PIP_TRUSTED_HOSTS when evaluating an
index specified at the command line when adding to Pipfile.
For example, this command line
PIP_TRUSTED_HOSTS=internal.mycompany.com pipenv install pypkg --index=https://internal.mycompany.com/pypi/simple
will add the following to the Pipfile:
[[source]]
url = 'https://internal.mycompany.com/pypi/simple'
verify_ssl = false
name = 'Internalmycompany'
[packages]
pypkg = {version="*", index="Internalmycompany"}
This allows users with private indexes to add them to Pipfile
initially from command line with correct permissions using environment
variable PIP_TRUSTED_HOSTS. #5572
Vendor in the updates, upgrades and fixes provided by pip==23.1. #5655
--skip-lock option with install command. #5653python-dotenv==1.0.0 #5656attrs==23.1.0 click-didyoumean==0.3.0 click==8.1.3 markupsafe==2.1.2 pipdeptree==2.7.0 shellingham==1.5.0.post1 tomlkit==0.11.7 #5657requirementslib==2.2.5 which includes updates for pip 23.1 #5659No significant changes.
2023.3.18 release. #5636--keep-outdated and --selective-upgrade which are deprecated for removal.
Introducing the pipenv upgrade command which takes the same package specifiers as pipenv install and
updates the Pipfile and Pipfile.lock with a valid lock resolution that only effects the specified packages and their dependencies.
Additionally, the pipenv update command has been updated to use the pipenv upgrade routine when packages are provided, which will install sync the new lock file as well. #5617pipenv now reads the system pip.conf or pip.ini file in order to determine pre-defined indexes to use for package resolution and installation. #5297pipenv check now checks the default packages group of the lockfile.
Specifying --categories to override which categories to check against.
Pass --use-installed to get the prior behavior of checking the packages actually installed into the environment. #5600CI env variable being set to something other than a truthy value. #5554--categories argument inconsistency between requirements command and install/sync by allowing comma separated values or spaces. #5570pipenv shell. #5603pip==23.0 release. #5586pip==23.0.1 minor pt release. Updates pythonfinder==1.3.2. #5614requirementslib hanging during install of remote wheels files. #5546--creator=venv by default; introduced two environment variables:
PIPENV_VIRTUALENV_CREATOR -- May be specified to instruct virtualenv which --creator= to use.
PIPENV_VIRTUALENV_COPIES -- When specified as truthy, instructs virtualenv to not use symlinks. #5477path is not propagated to the Pipfile.lock. #5479update --outdated raises NonExistentKey with outdated dev packages #5540pip==22.3.1 which is currently the latest version of pip. #5520pipenv check command has been broken in the published wheel distribution. #5493colorama due to regressions in core functionality. #5459install_search_all_sources is false (default behavior).
This fixes regression where install phase was using unexpected index after updating pip==22.3 #5444<pathed.module>:<func> and can also take arguments. For example: func = {call = "package.module:func('arg1', 'arg2')"} then this can be activated in the shell with pipenv run func #52942022.10.9 where Pipfile with pipenv section began generating new hash,
and also fix regression where lock phase did not update the hash value. #5394pipenv run pytest --markers--creator=venv when creating virtual environments to avoid issue with sysconfig posix_prefix on some systems. #5075requirementslib==2.0.3 to always evaluate the requirement markers fresh (without lru_cache) to fix marker determinism issue. #4660install --skip-lock with update to plette. #5368Remove usage of pipfile module in favour of Plette. pipfile is not actively maintained anymore. Plette is actively maintained, and has stricter checking of the Pipefile and Pipefile.lock. As a result, Pipefile with unnamed package indices will fail to lock. If a Pipefile was hand crafeted, and the source is anonymous an error will be thrown. The solution is simple, add a name to your index, e.g, replace:
[[source]]
url = "https://pypi.acme.com/simple"
verify_ssl = true
With:
[[source]]
url = "https://pypi.acme.com/simple"
verify_ssl = true
name = acmes_private_index `#5339 <https://github.com/pypa/pipenv/issues/5339>`_
pipenv path patch with importlib.util to eliminate import of pkg_resources #5349pip install by supplying --extra-pip-args="<arg1> <arg2>"
See the updated documentation Supplying additional arguments to pip for more details. #5283PIPENV_CUSTOM_VENV_NAME is more useful across projects. #5334pypiserver as a standalone process for all tests that referencce internal pypi artifacts.
General refactoring of some test cases to create more variety in packages selected--preferring lighter weight packages--in existing test cases.2022.9.2 where tarball URL packages were being skipped on batch_install. #5306pip resolver. #5273batch_install results in a faster and less CPU intensive pipenv sync or pipenv install experience. #5301pipenv now uses a NamedTemporaryFile for rsolver constraints and drops internal env var PIPENV_PACKAGES. #4925which_pip. #5314batch_install requirements in at most two invocations of pip install.
To see progress of install pass --verbose flag and pip progress will be output in realtime. #5315pipenv install --system on systems that having the python executable pointing to Python 2 and a Python 3 executable being python3. #5296constraints before resolving, which fixes pipenv lock generates nondeterminism environment markers. #5299requirementslib==2.0.1 which fixes issue with local install not marked editable, and vendor in vistir==0.6.1 which drops python2 support.
Drops orderedmultidict from vendoring. #5308setuptools and pkg_resources to avoid conflict upgrading setuptools.
Roll back sysconfig patch of pip because it was problematic for some --system commands. #5228requirementslib==2.0.0 and drop pip-shims entirely. #5228pythonfinder==1.3.1 #5292install_requires constraints from setup.py that depend on editable dependencies and could not resolve them. #5271pipenv lock fails for packages with extras as of 2022.8.13. #5274BAD_PACKAGES from batch_install in order for pipenv to install specific versions of setuptools.
To prevent issue upgrading setuptools this patches _USE_SYSCONFIG_DEFAULT to use sysconfig for 3.7 and above whereas pip default behavior was 3.10 and above. #5275pipenv install --system with a python3 but no python. #5261pipenv from site-packages and removed --ignore-installed argument from pip install in order to fix regressions with --use-site-packages. #5265pip_install method was using a different way of finding the python executable than other pipenv commands, which caused an issue with skipping package installation if it was already installed in site-packages. #5254packaging library from BAD_PACKAGES constant to allow it to be installed, which fixes regression from pipenv==2022.8.13. #5247CI or TF_BUILD is set but does not evaluate to False it is now treated as True. #5128pipenv commands that were still referencing the user or system installed pip to use the vendored pip internal to pipenv. #5229packages as constraints when locking dev-packages in Pipfile.
Use packages as constraints when installing new dev-packages. #5234pip update 22.2.2 #5230install -r or lock -r has been removed in favor of the pipenv requirements command. #5200pip_shims from the non vendored pipenv code, but retain initialization for requirementslib still has usages. #5204red in exception when getting hashes from pypi in _get_hashes_from_pypi. #5206subprocess_run directly to stdout instead of creating temporary file.
Remove deprecated distutils.sysconfig, use sysconfig. #5210notpip to pip in order to be clear that its a patched version of pip.pip, even for all types of installs.pip==22.2pipdeptree to not use pip-shims #5188urllib3 in favor of using it from vendored version in pip._vendor #5215NO_COLOR environment variable and deprecate PIPENV_COLORBLIND variable, which will be removed after this release. #5158no_deps for all other requirements in the loop causing a retry condition. #5164requirementslib for fix to lock when using editable VCS module with specific @ git reference. #5179pip==22.1.2 which upgrades pipenv from pip==22.0.4.
Vendor in latest version of requirementslib==1.6.7 which includes a fix for tracebacks on encountering Annotated variables.
Vendor in latest version of pip-shims==0.7.3 such that imports could be rewritten to utilize packaging from vendor'd pip.
Drop the packaging requirement from the vendor directory in pipenv. #5147normailze-charset. #5161funcsigs. #5168pyparsing==3.0.9. #5170pipenv requirements to add markers and add an --exclude-markers option to allow the exclusion of markers. #5092pipenv requirements #5134requests and certifi from vendored pip and remove them as explicit vendor dependencies. #5000requirementslib==1.6.5 which includes bug fixes for beta python versions, projects with an at sign (@) in the path, and a setuptools deprecation warning. #5132venv install scheme in Python.
First check if venv is among the available install schemes, and use it if it is. Otherwise fall back to the nt or posix_prefix install schemes as before. This should produce no change for environments where the install schemes were not redefined. #5096pipenv lock -r command printing to stdout instead of stderr. #5091requirements command problem by modifying to print -e and path of the editable package. #5070setuptools requirement in setup.py back to what it was in order to fix FileNotFoundError: [Errno 2] issue report. #5075requirementslib==1.6.4 to Fix SetuptoolsDeprecationWarning setuptools.config.read_configuration became deprecated. #5081pipenv packages' Metadata. #5065install_search_all_sources that allows installation of packages from an
existing Pipfile.lock to search all defined indexes for the constrained package version and hash signatures. #5041no_input flag, so the use of e.g Google Artifact Registry is possible. #4706pip from 21.2.2 to 22.0.4 which fixes a number of bugs including
several reports of pipenv locking for an infinite amount of time when using certain package constraints.
This also drops support for python 3.6 as it is EOL and support was removed in pip 22.x #4995more-itertools as it was originally added for zipp, which since stopped using it. #5044pipenv.vendor.vistir.compat.fs_str, since this function was used for PY2-PY3 compatibility and is no longer needed. #5062pipenv requirements command which generates a requirements.txt compatible output without locking. #4959.venv in the project when PIPENV_VENV_IN_PROJECT variable is False.
Unset variable maintains the existing behavior of preferring to use the project's .venv should it exist. #2763Pipfile.lock following package index restrictions added in pipenv==2022.3.23. #5023click was vendored into the project in
2021.11.9 because by default sphinx-click could no longer determine the CLI inherited from click. #4778install argument --extra-index-url as it was not compatible with index restricted packages.
Using the --index argument is the correct way to specify a package should be pulled from the non-default index. #5022process for change to Development processes.--quiet flag was set #5010requirementslib was not fully specifying the subdirectory to build_pep517 and
and when a new version of setuptools was released, the test test_lock_nested_vcs_direct_url
broke indicating the Pipfile.lock no longer contained the extra dependencies that should have been resolved.
This regression affected pipenv>=2021.11.9 but has been fixed by a patch to requirementslib. #5019Loading .env environment variables message on pipenv run
with the --quiet flag or the PIPENV_QUIET environment variable. #4027Loading .env environment variables... has been switched back to stderr as to not
break requirements.txt generation. Also it only prints now when a .env file is actually present. #5003PIPENV_SKIP_LOCK to control the behaviour of lock skipping. #4797verify, checks the Pipfile.lock is up-to-date #4893PIP_TARGET is set to environment variables, Refer specified directory for calculate delta, instead default directory #4775CI environment value, over mere existence of name #4944pythonfinder from 1.2.9 to 1.2.10 which fixes a bug with WSL
(Windows Subsystem for Linux) when a path can not be read and Permission Denied error is encountered. #4976--code from install and --unused from check.
Check command no longer takes in arguments to ignore.
Removed the vendored dependencies: pipreqs and yarg #4998charset-normalizer from 2.0.3 to 2.0.7, this fixes an import error on Python 3.6. #4865Pipfile when index url is given with pipenv install. #4873PIPENV_DONT_LOAD_ENV is set. #4851sys.executable when inside an activated venv. #4852jinja2 dependency as it is not needed any more. #4858click from 8.0.1 to 8.0.3, to fix a problem with bash completion. #4860chardet. #4862click-completion with click's own completion implementation. #4786pipenv run doesn't set environment variables correctly. #4831notpip's vendor library. This makes several objects of pip fail to be imported. #48333.10.0 can be found be python finder. #4837pythonfinder from 1.2.8 to 1.2.9. #4837pipenv shell fails to start a subshell. #4828pip_shims object isn't imported correctly. #4829pip commands when logging. #4760Update vendored dependencies
- attrs from 20.3.0 to 21.2.0
- cerberus from 1.3.2 to 1.3.4
- certifi from 2020.11.8 to 2021.5.30
- chardet from 3.0.4 to 4.0.0
- click from 7.1.2 to 8.0.1
- distlib from 0.3.1 to 0.3.2
- idna from 2.10 to 3.2
- importlib-metadata from 2.0.0 to 4.6.1
- importlib-resources from 3.3.0 to 5.2.0
- jinja2 from 2.11.2 to 3.0.1
- markupsafe from 1.1.1 to 2.0.1
- more-itertools from 5.0.0 to 8.8.0
- packaging from 20.8 to 21.0
- pep517 from 0.9.1 to 0.11.0
- pipdeptree from 1.0.0 to 2.0.0
- ptyprocess from 0.6.0 to 0.7.0
- python-dateutil from 2.8.1 to 2.8.2
- python-dotenv from 0.15.0 to 0.19.0
- pythonfinder from 1.2.5 to 1.2.8
- requests from 2.25.0 to 2.26.0
- shellingham from 1.3.2 to 1.4.0
- six from 1.15.0 to 1.16.0
- tomlkit from 0.7.0 to 0.7.2
- urllib3 from 1.26.1 to 1.26.6
- zipp from 1.2.0 to 3.5.0
Add new vendored dependencies
- charset-normalizer 2.0.3
- termcolor 1.1.0
- tomli 1.1.0
- wheel 0.36.2 #4747
Drop the dependencies for Python 2.7 compatibility purpose. #4751
Switch the dependency resolver from pip-tools to pip.
Update vendor libraries:
- Update requirementslib from 1.5.16 to 1.6.1
- Update pip-shims from 0.5.6 to 0.6.0
- New vendor platformdirs 2.4.0 #4759
importlib-metadata from the project's dependencies conflicts with that from pipenv's. #4549pep508checker.py did not expect double-digit Python minor versions (e.g. "3.10"). #4602packaging from 20.4 to 20.8. #4591pipenv run. #4368pipenv scripts under Windows platform. #4523colorama from 0.4.3 to 0.4.4
python-dotenv from 0.10.3 to 0.15.0first from 2.0.1 to 2.0.2iso8601 from 0.1.12 to 0.1.13parse from 1.15.0 to 1.18.0pipdeptree from 0.13.2 to 1.0.0requests from 2.23.0 to 2.25.0idna from 2.9 to 2.10urllib3 from 1.25.9 to 1.26.1certifi from 2020.4.5.1 to 2020.11.8requirementslib from 1.5.15 to 1.5.16attrs from 19.3.0 to 20.3.0distlib from 0.3.0 to 0.3.1packaging from 20.3 to 20.4six from 1.14.0 to 1.15.0semver from 2.9.0 to 2.13.0toml from 0.10.1 to 0.10.2cached-property from 1.5.1 to 1.5.2yaspin from 0.14.3 to 1.2.0resolvelib from 0.3.0 to 0.5.2pep517 from 0.8.2 to 0.9.1zipp from 0.6.0 to 1.2.0importlib-metadata from 1.6.0 to 2.0.0importlib-resources from 1.5.0 to 3.3.0 #4533pipenv scripts to display shortcuts from Pipfile. #3686--system option to pipenv sync. #4441--header/--no-header to pipenv lock command,
which adds a header to the generated requirements.txt #4443pexept.exceptions.TIMEOUT is not caught correctly because of the wrong import path. #4424pipenv install. #4436setup.py can't be parsed rightly. #4446venv directory will be mistaken as the editable package's metadata. #4480pipenv uninstall --all-dev.
From now on it does not uninstall regular packages. #3722--system flag is on. #4315pipenv uninstall throws an exception that does not exist. #4321setup.cfg of an editable package. #4335setup.py can't be parsed correctly when the assignment is type-annotated. #4342pipenv graph throws an exception that PipenvCmdError(cmd_string, c.out, c.err, return_code). #4388requirementslib to 1.5.12. #4385requirements to 1.5.13.pip-shims to 0.5.3. #4421venv and virtualenv based virtual environments more robustly. #4276+ signs in URL authentication fragments will no longer be incorrectly replaced with space ( `` `` ) characters. #4271/. #4273setup.py files with version variables read from os.environ are now able to be parsed successfully. #4274Pipfile.lock. #4278pipenv.cli.command. #4286setup.py. #4292., inside a venv based virtual environment. #4295pipenv install. #4296requirementslib AST parser which prevented parsing of setup.py files for dependency metadata. #42981.5.11. #42921.2.2 => 1.2.4
1.5.9 => 1.5.10 #4302pipenv install and pipenv sync will no longer attempt to install satisfied dependencies during installation. #3057,
#3506
Added support for resolution of direct-url dependencies in setup.py files to respect PEP-508 style URL dependencies. #3148
Added full support for resolution of all dependency types including direct URLs, zip archives, tarballs, etc.
stdout and stderr consistency. #3298For consistency with other commands and the --dev option
description, pipenv lock --requirements --dev now emits
both default and development dependencies.
The new --dev-only option requests the previous
behaviour (e.g. to generate a dev-requirements.txt file). #3316
Pipenv will now successfully recursively lock VCS sub-dependencies. #3328
Added support for --verbose output to pipenv run. #3348
ruff rules SIM by @cclauss in https://github.com/pypa/pipenv/pull/5873
Full Changelog: https://github.com/pypa/pipenv/compare/v2023.8.28...v2023.9.1
Nothing published for this version
clean-up of .rst leftovers in commands.md by @deronnax in https://github.com/pypa/pipenv/pull/5876
Full Changelog: https://github.com/pypa/pipenv/compare/v2023.8.26...v2023.8.28
pre-commit autoupdate 2023-08-25 by @cclauss in https://github.com/pypa/pipenv/pull/5867
Full Changelog: https://github.com/pypa/pipenv/compare/v2023.8.25...v2023.8.26
Adjust the Fallback logic for obtaining the hashes from private indexes by @matteius in https://github.com/pypa/pipenv/pull/5866
Full Changelog: https://github.com/pypa/pipenv/compare/v2023.8.23...v2023.8.25
One column per quarter.