No description, website, or topics provided.



Pipfile and its sister Pipfile.lock are a replacement for the existing standard pip's requirements.txt file.

WARNING: This project is under active design and development. Nothing is set in stone at this point of time.

This repository contains the design specification of the Pipfile format, as well as (soon) an implementation of a parser for the specification which can be used by pip and any other consumer, once the design (including the form of a Pipfile itself) has been built out and finalized.

The Concept

Pipfile will be superior to requirements.txt file in a number of ways:

  • TOML syntax for declaring all types of Python dependencies.
  • One Pipfile (as opposed to multiple requirements.txt files).
    • Existing requirements files tend to proliferate into multiple files - e.g. dev-requirements.txt, test-requirements.txt, etc. - but a Pipfile will allow seamlessly specifying groups of dependencies in one place.
    • This will be surfaced as only two built-in groups (default & development). (see note below)
  • Fully specified (and deterministic) environments in the form of Pipfile.lock. A deployed application can then be completely redeployed with the same exact versions of all recursive dependencies, by referencing the Pipfile.lock file.

The concrete requirements for a Python Application would come from Pipfile. This would include where the packages should be fetched from and their loose version constraints.

The details of the environment (all installed packages with pinned versions and other details) would be stored in Pipfile.lock, for reproducibility. This file will be automatically generated and should not be modified by the user.

NOTE: Custom groups may be added in the future. Remember, it is easier to add features in the future than it is to remove them.

The Composer community has been successful with only default and development as group options for many years. This model would be tried/followed at first.


NOTE: This is an evolving work in progress.


url = ''
verify_ssl = true

python_version = '2.7'

requests = { extras = ['socks'] }
Django = '>1.10'
pinax = { git = 'git://', ref = '1.4', editable = true }

nose = '*'


  • There will be a default source.

PEP 508 Support

# Support for all PEP 508 markers
python_full_version = '3.6.0b1'

platform = 'windows'

requires utilizes PEP 508 marker = 'specifier' markers. This functionality may not be readily used, as it is only to assert (and therefore abort, if appropriate) installation on certain platforms (e.g. python version, platform version).


    "_meta": {
        "hash": {
            "sha256": "73d81f4fbe42d1da158c5d4435d921121a4a1013b2f0dfed95367f3c742b88c6",
        "requires": [
            {"marker": "python_version", "specifier": "2.7"}
        "sources": [
            {"url": "", "verify_ssl": true},
    "default": [
        {"name": "Django", "version": "1.10.3", "hash": "..."},
        {"name": "requests", "version": "2.12.1", "hash": "..."},
        {"name": "pinax", "git": "git://...", "ref": "1.4", "editable": true},
        {"name": "PySocks", "version": "1.5.6", "hash": "..."},
    "development": [
        {"name": "nose", "version": "1.3.7", "hash": "..."},

Pipfile.lock is always to be generated and is not to be modified or constructed by a user.

Do note how the versions of each dependency are recursively frozen and a hash gets computed so that you can take advantage of new pip security features

Pip Integration (eventual)

pip will grow a new command line options, -p / --pipfile to install the versions as specified in a Pipfile, similar to its existing -r / --requirement argument for installing requirements.txt files.

Install packages from Pipfile:

$ pip install -p
! Warning: Pipfile.lock (48d35f) is out of date. Updating to (73d81f).
Installing packages from requirements.piplock...
[installation output]

To manually update the Pipfile.lock:

$ pip freeze -p different_pipfile
different_pipfile.lock (73d81f) written to disk.


# -p accepts a path argument, which defaults to 'Pipfile'.
# Pipfile.lock will be written automatically during `install -p` if it does not exist.


- Recursively look for `Pipfile` in parent directories (limit 3/4?) when ``-p`` is bare.

Useful Links


  • nvie/pip-tools: A set of tools to keep your pinned Python dependencies fresh.
  • A Better Pip Workflow by Kenneth Reitz
  • Lessons learned from Composer, Cargo, Yarn, NPM, Bundler and friends.


The documentation for this project will, eventually, reside at


If you run into bugs, you can file them in our issue tracker. You can also join #pypa on Freenode to ask questions or get involved.

Code of Conduct

Everyone interacting in the pipfile project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the PyPA Code of Conduct.