> On Mar 17, 2015, at 8:33 AM, Paul Moore <[email protected]> wrote: > > On 17 March 2015 at 11:49, Donald Stufft <[email protected]> wrote: >>> I'm still not clear what you expect pip to *do* with the metadata. >>> It's just data, there's no functionality specified in the PEP. >> >> What pip does now with metadata, Look at it for dependency information when >> installing the Wheel, show it when doing ``pip show``, handle the Provides >> metadata making something “Provide” something else, show warnings for the >> obsoleted-by metadata, handle extensions (including failing if there is a >> critical extension we don’t understand). > > Hmm, OK. > > At the moment that stuff (except pip show) is all covered by the > running of the egg_info command, I guess. So you're saying that pip > should first check if a requirement has new-style metadata and if it > does, skip the egg_info command and use pydist.json. I guess that > would be good - it'd solve the problems we see with numpy-related > packages that need things installed just to run setup.py egg_info. > > It wasn't something I'd particularly considered, but thanks for the > clarification. > > Paul
There is no egg_info command inside of a Wheel, it’s currently looking at foo.whl/foo.dist-info/METADATA for that. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
