Development Philosophy — pipenv documentation

From Get docs

Development Philosophy

Pipenv is an open but opinionated tool, created by an open but opinionated developer.

Management Style

To be updated (as of March 2020).

Kenneth Reitz is the BDFL. He has final say in any decision related to the Pipenv project. Kenneth is responsible for the direction and form of the library, as well as its presentation. In addition to making decisions based on technical merit, he is responsible for making decisions based on the development philosophy of Pipenv.

Dan Ryan, Tzu-ping Chung, and Nate Prewitt are the core contributors. They are responsible for triaging bug reports, reviewing pull requests and ensuring that Kenneth is kept up to speed with developments around the library. The day-to-day managing of the project is done by the core contributors. They are responsible for making judgments about whether or not a feature request is likely to be accepted by Kenneth.


  • Simplicity is always better than functionality.
  • Listen to everyone, then disregard it.
  • The API is all that matters. Everything else is secondary.
  • Fit the 90% use-case. Ignore the nay-sayers.