pipenv

Create virtual environment and install packages

$ pipenv install [requests]

$ pipenv install --dev [pytest]

$ pipenv install

$ pipenv shell

$ pipenv run [python script.py]

$ pipenv requirements > requirements.txt

$ pipenv graph

$ pipenv --rm

pipenv command [options] [packages]

pipenv combines pip and virtualenv into a single workflow. It manages project dependencies with Pipfile/Pipfile.lock files, similar to npm's package.json or Ruby's Bundler.
The Pipfile replaces requirements.txt with a more structured format. It separates production and development dependencies. The Pipfile.lock ensures deterministic builds by pinning exact versions and hashes.
Virtual environments are created automatically per project. The shell command activates the environment, while run executes commands within it without manual activation. Environment location is determined by the project directory.
Security features include hash verification of packages and vulnerability scanning via check command. The graph command visualizes the dependency tree, helping understand transitive dependencies.
Pipenv integrates with .env files, automatically loading environment variables. This keeps secrets separate from code while making them available during development.

install [packages]

Install packages and add to Pipfile.

Remove packages from environment.

Generate Pipfile.lock.

Install packages from Pipfile.lock.

Spawn shell in virtual environment.

Run command in virtual environment.

Show dependency graph.

Check for security vulnerabilities.

Generate requirements.txt output.

Update packages.

Remove packages not in Pipfile.lock.

Include dev dependencies.

Specify Python version.

Show virtual environment path.

Remove virtual environment.

Show project home.

Use Python 3 / Python 2.

Enable system site-packages.

Lock resolution can be slow for complex dependencies. Not as fast as newer tools like Poetry or uv. Hash verification requires packages have published hashes. Some edge cases in dependency resolution. May conflict with system-wide pip packages.

pipenv was created by Kenneth Reitz (author of requests) around 2017. It aimed to bring the developer experience of npm/Bundler to Python. PyPA endorsed it as a recommended tool. While newer alternatives like Poetry have emerged, pipenv remains widely used for its simplicity and integration with pip.

pip(1), poetry(1), virtualenv(1), uv(1)