Pipenv icon
Pipenv icon

Pipenv

Pipenv is a production-ready tool that aims to bring the best of all packaging worlds to the Python world. It harnesses Pipfile, pip, and virtualenv into one single command.

Cost / License

  • Free
  • Open Source (MIT)

Platforms

  • Python
  • Mac
  • Windows
  • Linux
  • BSD
-
No reviews
0likes
0comments
0news articles

Features

Suggest and vote on features
  1.  Supports Python
  2.  Python-based

 Tags

Pipenv News & Activities

Highlights All activities

Recent activities

Show all activities

Pipenv information

  • Developed by

    Python Packaging Authority
  • Licensing

    Open Source (MIT) and Free product.
  • Written in

  • Alternatives

    14 alternatives listed
  • Supported Languages

    • English

AlternativeTo Category

Development

GitHub repository

  •  25,105 Stars
  •  1,875 Forks
  •  154 Open Issues
  •   Updated  
View on GitHub

Popular alternatives

View all
Pipenv was added to AlternativeTo by Paul on and this page was last updated .
No comments or reviews, maybe you want to be first?
Post comment/review

What is Pipenv?

Pipenv is a Python virtualenv management tool that supports a multitude of systems and nicely bridges the gaps between pip, python (using system python, pyenv or asdf) and virtualenv. Linux, macOS, and Windows are all first-class citizens in pipenv.

Pipenv automatically creates and manages a virtualenv for your projects, as well as adds/removes packages from your Pipfile as you install/uninstall packages. It also generates a project Pipfile.lock, which is used to produce deterministic builds.

Pipenv is primarily meant to provide users and developers of applications with an easy method to arrive at a consistent working project environment.

The problems that Pipenv seeks to solve are multi-faceted:

  • You no longer need to use pip and virtualenv separately: they work together.
  • Managing a requirements.txt file with package hashes can be problematic. Pipenv uses Pipfile and Pipfile.lock to separate abstract dependency declarations from the last tested combination.
  • Hashes are documented in the lock file which are verified during install. Security considerations are put first.
  • Strongly encourage the use of the latest versions of dependencies to minimize security risks arising from outdated components.
  • Gives you insight into your dependency graph (e.g. $ pipenv graph).
  • Streamline development workflow by supporting local customizations with .env files.

Official Links