Also if someone with pip write access could please discuss and hopefully merge my initial PR on pip, I would very much appreciate it. Paul seems to be short on time.

2017-09-04 19:09 GMT-05:00 xoviat <xoviat@gmail.com>:
Nathaniel:

Pip requires egg_info to discover dependencies of source distributions so that it can build wheels all at once after downloading the requirements. I need to move pip off of egg_info as soon as possible and dist_info is required to do that.

2017-09-03 21:00 GMT-05:00 Nathaniel Smith <njs@pobox.com>:
On Sun, Sep 3, 2017 at 11:14 AM, xoviat <xoviat@gmail.com> wrote:
> Just an update for everyone here:
>
> 1. We're currently waiting on the implementation of the 'dist_info" command
> in the wheel project.
> 2. Once that is done we can switch pip over to reading dist-info rather than
> egg_info.
> 3. Then we can move the backend over to setuptools. Because Jacob has a much
> more efficient release system than pip, I anticipate having a release of
> setuptools first and then we can switch pip over to requiring a newer
> setuptools via PEP 518.

I don't think pip actually has any use for the PEP 517
prepare_wheel_metadata hook right now though? Historically 'setup.py
egg-info' was needed to kluge around unwanted behavior in 'setup.py
install', but with a PEP 517 backend that's irrelevant because
'setup.py install' is never used. And in the future when pip has a
real resolver, then prepare_wheel_metadata should allow some
optimizations. But right now, prepare_wheel_metadata is completely
useless AFAIK.

So why is 'setup.py dist_info' a blocker for things?

-n

--
Nathaniel J. Smith -- https://vorpus.org