<div dir="auto">Supposedly there is some meeting tomorrow concerning the wheel project that will determine the fate of dist_info. So that is why I bought it up.</div><div class="gmail_extra"><br><div class="gmail_quote">On Sep 4, 2017 9:00 PM, "Chris Jerdonek" <<a href="mailto:chris.jerdonek@gmail.com">chris.jerdonek@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Sep 4, 2017 at 6:41 PM, xoviat <<a href="mailto:xoviat@gmail.com">xoviat@gmail.com</a>> wrote:<br>
> The PR that I am taking about is not for pip but for the wheel project.<br>
<br>
Okay, well you started the thread asking something similar for your<br>
pip PR (see below). I'm sure similar considerations hold for the wheel<br>
project.<br>
<br>
On Mon, Sep 4, 2017 at 5:11 PM, xoviat <<a href="mailto:xoviat@gmail.com">xoviat@gmail.com</a>> wrote:<br>
> Also if someone with pip write access could please discuss and hopefully<br>
> merge my initial PR on pip, I would very much appreciate it. Paul seems to<br>
> be short on time.<br>
<br>
--Chris<br>
<br>
<br>
><br>
> On Sep 4, 2017 8:19 PM, "Chris Jerdonek" <<a href="mailto:chris.jerdonek@gmail.com">chris.jerdonek@gmail.com</a>> wrote:<br>
>><br>
>> On Mon, Sep 4, 2017 at 6:08 PM, xoviat <<a href="mailto:xoviat@gmail.com">xoviat@gmail.com</a>> wrote:<br>
>> > In any case, we're going to need this for prepare_metadata, so the<br>
>> > question<br>
>> > you should ask is: what are the reasons for *not* merging this? I<br>
>> > haven't<br>
>> > heard any so far but that doesn't mean that they don't exist. If there<br>
>> > are<br>
>> > none, then I don't see why we cannot merge my wheel PR and do a release.<br>
>><br>
>> FYI, you're not the only one waiting for PR's to be merged. There are<br>
>> 56 other PR's, some of which have already been approved by repo<br>
>> members with commit access. I would try to be a little more patient.<br>
>> Otherwise, everyone can be emailing the list saying the same thing and<br>
>> asking why their PR isn't being merged.<br>
>><br>
>> --Chris<br>
>><br>
>> ><br>
>> > 2017-09-04 19:51 GMT-05:00 xoviat <<a href="mailto:xoviat@gmail.com">xoviat@gmail.com</a>>:<br>
>> >><br>
>> >> > The only reason I can think of that setuptools would need a dist_info<br>
>> >> command would be to implement the PEP 517 prepare_wheel_metadata hook.<br>
>> >><br>
>> >> Yes. That is absolutely correct.<br>
>> >><br>
>> >> > But this hook is optional and in fact provides no value right now, so<br>
>> >> it can't be a blocker for anything.<br>
>> >><br>
>> >> The simplest way to start on this issue is to replace egg_info in pip<br>
>> >> with<br>
>> >> prepare_metadata_for_build_<wbr>wheel. It is absolutely a historical<br>
>> >> artifact but<br>
>> >> I need to work on one issue at a time. The next issue will be replacing<br>
>> >> egg_info in pip with prepare_metadata_for_build_<wbr>wheel.<br>
>> >><br>
>> >> 2017-09-04 19:34 GMT-05:00 Nathaniel Smith <<a href="mailto:njs@pobox.com">njs@pobox.com</a>>:<br>
>> >>><br>
>> >>> On Mon, Sep 4, 2017 at 5:09 PM, xoviat <<a href="mailto:xoviat@gmail.com">xoviat@gmail.com</a>> wrote:<br>
>> >>> > Nathaniel:<br>
>> >>> ><br>
>> >>> > Pip requires egg_info to discover dependencies of source<br>
>> >>> > distributions<br>
>> >>> > so<br>
>> >>> > that it can build wheels all at once after downloading the<br>
>> >>> > requirements. I<br>
>> >>> > need to move pip off of egg_info as soon as possible and dist_info<br>
>> >>> > is<br>
>> >>> > required to do that.<br>
>> >>><br>
>> >>> "Requires" is a strong word -- AFAIK this is just a historical<br>
>> >>> artifact. I don't really know what you're talking about in the second<br>
>> >>> sentence.<br>
>> >>><br>
>> >>> The only reason I can think of that setuptools would need a dist_info<br>
>> >>> command would be to implement the PEP 517 prepare_wheel_metadata hook.<br>
>> >>> But this hook is optional and in fact provides no value right now, so<br>
>> >>> it can't be a blocker for anything. (In fact I can't see any reason<br>
>> >>> why pip would ever call it before the resolver lands.) So either (a)<br>
>> >>> there's some other reason you want a dist_info command, (b) there's<br>
>> >>> some reason I'm missing why prepare_wheel_metadata matters, or (c) one<br>
>> >>> of us is misunderstanding something :-).<br>
>> >>><br>
>> >>> -n<br>
>> >>><br>
>> >>> > 2017-09-03 21:00 GMT-05:00 Nathaniel Smith <<a href="mailto:njs@pobox.com">njs@pobox.com</a>>:<br>
>> >>> >><br>
>> >>> >> On Sun, Sep 3, 2017 at 11:14 AM, xoviat <<a href="mailto:xoviat@gmail.com">xoviat@gmail.com</a>> wrote:<br>
>> >>> >> > Just an update for everyone here:<br>
>> >>> >> ><br>
>> >>> >> > 1. We're currently waiting on the implementation of the<br>
>> >>> >> > 'dist_info"<br>
>> >>> >> > command<br>
>> >>> >> > in the wheel project.<br>
>> >>> >> > 2. Once that is done we can switch pip over to reading dist-info<br>
>> >>> >> > rather<br>
>> >>> >> > than<br>
>> >>> >> > egg_info.<br>
>> >>> >> > 3. Then we can move the backend over to setuptools. Because Jacob<br>
>> >>> >> > has a<br>
>> >>> >> > much<br>
>> >>> >> > more efficient release system than pip, I anticipate having a<br>
>> >>> >> > release of<br>
>> >>> >> > setuptools first and then we can switch pip over to requiring a<br>
>> >>> >> > newer<br>
>> >>> >> > setuptools via PEP 518.<br>
>> >>> >><br>
>> >>> >> I don't think pip actually has any use for the PEP 517<br>
>> >>> >> prepare_wheel_metadata hook right now though? Historically<br>
>> >>> >> 'setup.py<br>
>> >>> >> egg-info' was needed to kluge around unwanted behavior in 'setup.py<br>
>> >>> >> install', but with a PEP 517 backend that's irrelevant because<br>
>> >>> >> 'setup.py install' is never used. And in the future when pip has a<br>
>> >>> >> real resolver, then prepare_wheel_metadata should allow some<br>
>> >>> >> optimizations. But right now, prepare_wheel_metadata is completely<br>
>> >>> >> useless AFAIK.<br>
>> >>> >><br>
>> >>> >> So why is 'setup.py dist_info' a blocker for things?<br>
>> >>> >><br>
>> >>> >> -n<br>
>> >>> >><br>
>> >>> >> --<br>
>> >>> >> Nathaniel J. Smith -- <a href="https://vorpus.org" rel="noreferrer" target="_blank">https://vorpus.org</a><br>
>> >>> ><br>
>> >>> ><br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> --<br>
>> >>> Nathaniel J. Smith -- <a href="https://vorpus.org" rel="noreferrer" target="_blank">https://vorpus.org</a><br>
>> >><br>
>> >><br>
>> ><br>
</blockquote></div></div>