On Thu, Aug 22, 2013 at 4:24 AM, Paul Moore <p.f.mo...@gmail.com> wrote: > On 21 August 2013 23:20, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote: >> >> Nick Coghlan <ncoghlan <at> gmail.com> writes: >> >> > Um, the current wheel spec uses PEP 345 + setuptools metadata only. If >> distlib is expecting PEP 426 metadata in wheel files, it is not compliant >> with >> the spec. >> >> I can certainly rectify that - I was possibly confused by the fact that >> the >> latest wheel implementation writes pydist.json to the wheel (though the >> Wheel- >> Version in WHEEL is still 1.0). > > > Conversely, of course, there's no mention in the wheel spec that setuptools > metadata (specifically entry-points.txt) should be present. Which is why I > mentioned that the wheel spec might need a review/update to clarify this (if > we want to ensure that any necessary script metadata is guaranteed to be > present in compliant wheels).
pydist.json is in there in order to have an implementation / old metadata converter to inform PEP 426 development. I added the "generator" tag to PEP 426 to deal with the problem of detecting pydist.json that conform to obsolete drafts of the spec. In the meantime the stable metadata is what setuptools supports inside .dist-info directories which is similar to old-draft key/value PEP 426, including Provides-Extra: etc. Apart from the upcoming wrapper scripts generation, the basic wheel install step shouldn't need to read any of the setuptools/PEP 345/426 metadata at all. _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
