pypa/pip

Requirements 2.0

dstufft opened this issue · 9 comments

dstufft commented

A general ticket to start defining what requirements 2.0 looks like and to figure out what the requirements are for such a new file.

piotr-dobrogost commented

Interesting question seems to be to what degree semantics of the process of installation of requirements should be defined in this specification. Compare issue #56 and issue #278 for example.

dstufft commented

Here are two gists I made previously that sketched out some ideas I had around a new requirements format:

kennethreitz commented

I am interested in helping come up with the names of these new files (and possibly the names of the api components).

dstufft commented

I created pypa/pipfile to provide a place to begin work on this, since ideally this would be a library that pip can consume so that people other than pip can parse these files too.

  • 👍12
  • ❤️11
kennethreitz commented

updating the readme to reflect the concepts

kennethreitz commented

work is underway!

dstufft commented

See #3772 for a case that we should handle better with requirements 2.0 (if we're not already).

pradyunsg commented

@dstufft Can we close this?

pipfile's issue tracker and pypa-dev (not distutils-sig :3) should be the right places to discuss this; correct?

dstufft commented

Yea.