pipfile

It requires a lot of work to produce reproducible/secure builds, see the original Pipfile design discussion for gory details: https://github.com/pypa/pipfile

In defense of double brackets, I first encountered TOML in pipenv[1], and just by experimenting found I could add another source. So they're reasonably obvious if you see them in an existing file. [1]: https://github.com/pypa/pipfile#pipfile

Pipenv combines package management and virtualenv managment in one tool. You can create a new project as simple as this: $ mkdir myproj $ cd myproj $ pipenv --python 3.6 # This creates a virtualenv with Python 3.6 for you project. $ pipenv install flask # This installs flask in your virtualenv. $ pipenv run flask # This runs flask in your virtualenv. $ pipenv run python # This runs a REPL with the interpreter of your venv. $ pipenv shell # This opens a shell in your venv. Pipenv replaces requirements.txt with Pipfile and Pipfile.lock. (Similar to what you get from npm or yarn in the JS world, and cargo in Rust) If you use pipenv for a project, you no longer need to care about pip, requirements.txt or virtualenv. Pipenv/Pipfile is the new standard recommended b

One thing in particular Pipenv/pipfile needs to address is a standardised calculation of the hashed virtualenv paths. I tried creating a PR for SublimeText's Anaconda plugin, and realised that right now it requires 4(!) separate subprocess calls, each of which starts a Python process to simply get the path of the current project's virtualenv. Until there is a very simple way (a max. 10-20 line function) to calculate this path, including a reference implementation in Python and JS, there is no way widespread editor support can happen. https://github.com/pypa/pipfile/issues/88 https://github.com/pypa/pipenv/issues/985 https://github.com/DamnWidget/anaconda/issues/717 https://github.com/DamnWidget/anaconda/pull/720