> On Jan 15, 2016, at 9:12 AM, Paul Moore <p.f.mo...@gmail.com> wrote: > > Pip refers to PEP 440 when defining the format of a requirement (see > https://pip.pypa.io/en/stable/reference/pip_install/#requirement-specifiers). > But PEP 508 *also* defines a requirement - the title implies that it's > for dependency specification, but the content of the PEP says "the > language defined is a compact line based format which is already in > widespread use in pip requirements files". > > So what's the relationship between PEP 440 and PEP 508? Which one is > the definitive definition of what is a "requirement"? The "packaging" > library implements specifiers which conform (according to the docs) to > PEP 440. > > IMO, we're in danger of switching from having too few standards to > having too many... > > Can someone clarify? > Thanks, > Paul > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig
A PEP 508 requirement contains a PEP 440 specifier. E.g. something like `requests >= 1.0` is a PEP 508 requirement format, which contains a distribution name `requests` and a PEP 440 version specifier `>= 1.0`. ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
