Open-source project
pypa/pipenv avatar
pypa/pipenv

Pipenv ties pip and virtualenv to a Pipfile, and the 2026.5.0 completion change breaks old shells

Python Development Workflow for Humans.

25,024 stars1,888 forksPythonMIT

At a glance

What is it?
Pipenv creates a virtualenv per project, edits a Pipfile as you install packages, and writes a hashed Pipfile.lock. It requires Python 3.11 or newer and ships releases every few days.
Who is it for?
Pick Pipenv if you build Python applications and want pip, a virtualenv and hash-checked locking behind one command, and you run Python 3.11 or newer. Skip it for libraries that publish a requirements-style metadata flow of their own, and check your shell completion setup first if you are upgrading from a release before 2026.5.0.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly Python, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • pypa/pipenv25,024 ★ · -1
Star history
Repository2026-10-082026-11-15
pypa/pipenv25k25k

-1 Stars in the last 38 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

A Pipfile holds intent and Pipfile.lock holds the last tested set

Pipenv automatically creates and manages a virtualenv for each project, and it adds or removes entries in the Pipfile as you install or uninstall packages. It also generates Pipfile.lock, which it uses to produce deterministic builds.

The split is the core design. A requirements.txt with package hashes is awkward to maintain by hand, so Pipenv keeps the abstract dependency declaration in the Pipfile and the last tested combination in the lock file. Hashes are recorded in the lock file and verified at install time. If a downloaded file does not match, the install does not accept it.

Basic behavior follows from that. When you pass no parameters to install, everything in [packages] is installed. A virtualenv is created if none exists. Pipenv finds the project home by searching recursively for a Pipfile, and generates a Pipfile if there is none. Run it from a subdirectory and it still finds the right project; run it in a fresh directory and it quietly starts a new one, which is easy to do by accident.

Python 3.11 is the floor, and Python 3.15 is already in the classifiers

The README states that Pipenv installs with Python 3.11 and above, including Python 3.15. The pyproject.toml sets requires-python to >=3.11 and lists classifiers for 3.11 through 3.15, on CPython and PyPy. The Makefile's PY_VERSIONS covers the same range: 3.11, 3.12, 3.13, 3.14 and 3.15.

If your project or your CI image is on Python 3.10 or older, the current release will not install there. You would need an older Pipenv.

The runtime dependencies are short: certifi, filelock 4.2.1 or newer, packaging 22 or newer, setuptools 84.1.0 or newer and virtualenv 21.14.9 or newer. Optional groups cover argcomplete for completion, safety 3.0.0 or newer, and test and dev tooling. Because Pipenv pins a very new virtualenv, installing it into a shared system Python can upgrade packages other tools rely on, which is one reason to prefer an isolated install.

Six ways to install it, and pip install --user leaves you hunting for PATH

The recommended method is pip:

code
pip install --user pipenv

The README also lists system packages. FreeBSD uses `pkg install py39-pipenv`, Gentoo uses `sudo emerge pipenv`, and Void Linux uses `sudo xbps-install -S python3-pipenv`. The FreeBSD package name mentions py39, which sits below the Python 3.11 floor stated for the current release, so check what version that package actually installs.

Two more options exist. Pipx isolates the tool from your project interpreters:

code
pipx install pipenv

And the plain module form is `python -m pip install pipenv`. The README points to the official documentation for the latest instructions.

The README does not explain how to fix a missing pipenv command after a --user install. That is a common stumbling block, since the user scripts directory has to be on PATH. Pipx handles that step through its own path setup, and the repository also ships get-pipenv.py at the top level, although the README does not describe it.

Shell completion moved to argcomplete and broke the old environment variable

Completion is powered by argcomplete, which is an optional dependency:

code
pip install "pipenv[completion]"

For zsh, add this to ~/.zshrc:

code
autoload -U bashcompinit
bashcompinit
eval "$(register-python-argcomplete pipenv)"

Bash, including Git Bash on Windows, needs only the eval line in ~/.bashrc or ~/.bash_profile. For fish, add `register-python-argcomplete --shell fish pipenv | source` to ~/.config/fish/completions/pipenv.fish. A fish plugin exists that activates your subshells automatically.

The breaking part is a note in the README: if you upgrade from a version older than 2026.5.0, the old _PIPENV_COMPLETE environment variable method no longer works. Your existing dotfile line will silently stop completing, and the fix is to replace it with the register-python-argcomplete commands above and reload your shell.

The option list shows diagnostics, a PyPI mirror flag and environment variables

Running `pipenv --help` prints the global options. The location queries are --where for project home, --venv for virtualenv information, --py for the interpreter and --envs for environment variable options. --rm removes the virtualenv. --support outputs diagnostic information for use in GitHub issues, which is the thing to paste when you file a bug.

Some options carry environment variables. --site-packages and --no-site-packages map to PIPENV_SITE_PACKAGES, and --clear, which clears the pipenv and pip caches, maps to PIPENV_CLEAR. --python TEXT picks which Python the virtualenv uses, and --pypi-mirror TEXT sets a PyPI mirror. Quiet, verbose and bare output modes are -q, -v and --bare.

The feature list adds that Pipenv will install a required Python automatically when pyenv or asdf is available, and that it loads .env files if they exist. Both are conveniences with a cost: a .env file in the project directory is read without a flag, so keep secrets out of any file you commit. The README also notes that `pipenv graph` shows your dependency graph.

Releases arrive several times a month under date-based version numbers

The repository is not archived and the last push was on 1 November 2026. Recent releases are v2026.10.3 on 25 October, v2026.10.4 on 28 October and v2026.10.5 on 1 November 2026. Versions follow a year, month and counter pattern, so the number tells you when it was cut and not whether anything breaking changed.

That cadence matters for pinning. The shell completion break at 2026.5.0 was introduced in a release just like the others, so reading the news directory and CHANGELOG.md before upgrading is the only way to see it coming. The repository also holds planning documents named initiative-g-phase1-2-plan.md and two phase 3 files at the top level, and a pylock.toml alongside the Pipfile, with an example Pipfile.with_pylock under examples. Treat the pylock work as something to check in docs/ before relying on it.

Pipenv is MIT licensed, with a homepage at pipenv.pypa.io. Its stated audience is users and developers of applications who want a consistent working environment, which is narrower than packaging libraries for others to install.

Editorial conclusion

Pick Pipenv if you build Python applications and want pip, a virtualenv and hash-checked locking behind one command, and you run Python 3.11 or newer. Skip it for libraries that publish a requirements-style metadata flow of their own, and check your shell completion setup first if you are upgrading from a release before 2026.5.0.

Frequently asked questions

What is pipenv used for?

Pipenv creates and manages a virtualenv for a project, records packages in a Pipfile, and writes a Pipfile.lock with hashes for deterministic builds.

How to install pipenv?

The README recommends pip install --user pipenv, and also lists pipx install pipenv and python -m pip install pipenv. It requires Python 3.11 or above.

Which is better, pipenv or pyenv?

They do different jobs. Pipenv manages virtualenvs and the Pipfile, and it can install required Pythons automatically when pyenv or asdf is available.

How to use pipenv?

Run pipenv install in a project directory. It creates a virtualenv if none exists and installs everything in [packages]. Use pipenv --help to see all commands and options.

Official sources

  1. License: MIT
  2. Project website
  3. pypa/pipenv on GitHub
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/pypa-pipenv.svg)](https://hysenlabs.com/projects/pypa-pipenv)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/pypa-pipenv.svg)](https://hysenlabs.com/projects/pypa-pipenv)

Was this useful?