I could be wrong but if egg-info actually generated a dist-info directory it would probably still work.
On Mon, Oct 12, 2015 at 8:50 AM Thomas Kluyver <[email protected]> wrote: > On 12 October 2015 at 05:37, Robert Collins <[email protected]> > wrote: > >> And a bugfix :) - I didn't link to the docs for the build system >> interface we have today - >> >> https://pip.pypa.io/en/latest/reference/pip_install/#build-system-interface >> > > I'm happy to see that the command line interface pip requires from > setup.py is now documented. But the first thing it describes is the > egg_info command, and the description of what that involves is basically > 'whatever setuptools does'. Egg info is not any kind of standard, AFAIK - > unlike dist info. One of my main goals in writing flit is to build wheels > without involving setuptools at all, so I'm probably never going to > implement that. > > I also don't want to have a setup.py in the VCS at all, because it's an > invitation for people to run setup.py whatever, and then file bug reports > that it doesn't do exactly what setuptools/distutils would do. > > This is what I like about Nathaniel's proposal. By looking for a new file, > it clearly indicates that this is a new style Python source tree, without > potential confusion over what setup.py does, and it lets us specify a > simple build system interface based on standardised pieces like wheels > rather than messing around with the details of setuptools. > > Thomas > _______________________________________________ > Distutils-SIG maillist - [email protected] > https://mail.python.org/mailman/listinfo/distutils-sig >
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
