<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 16, 2015, at 7:03 PM, Nick Coghlan <<a href="mailto:ncoghlan@gmail.com" class="">ncoghlan@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p dir="ltr" class=""><br class="">
On 17 Mar 2015 02:33, "Daniel Holth" <<a href="mailto:dholth@gmail.com" class="">dholth@gmail.com</a>> wrote:<br class="">
><br class="">
> Problem: Users would like to be able to import stuff in setup.py. This<br class="">
> could be anything from a version fetcher to a replacement for<br class="">
> distutils itself. However, if setup.py is the only place to specify<br class="">
> these requirements there's a bit of a chicken and egg problem, unless<br class="">
> they have unusually good setuptools knowledge, especially if you want<br class="">
> to replace the entire setup() implementation.<br class="">
><br class="">
> Problem: Having easy_install do it is not what people want and misses<br class="">
> some important use cases.<br class="">
><br class="">
> Problem: Based on empirical evidence PEP 426 will never be done. Its<br class="">
> current purpose is to shut down discussion of pragmatic solutions.</p><p dir="ltr" class="">Slight correction here: one of my current aims with PEP 426 is deliberately discouraging the discussion of solutions that only work reliably if everyone switches to a new build system first. That's a) never going to happen; and b) one of the key mistakes the distutils2 folks made that significantly hindered adoption of their work, and I don't want us to repeat it.</p><p dir="ltr" class="">My other key aim is to provide a public definition of what I think "good" looks like when it comes to software distribution, so I can more easily assess whether less radical proposals are still moving us closer to that goal.</p><p dir="ltr" class="">Making pip (and perhaps easy_install) setup.cfg aware, such that it assumes the use of d2to1 (or a semantically equivalent tool) if setup.cfg is present and hence is able to skip invoking setup.py in relevant cases, sounds like just such a positive incremental step to me, as it increases the number of situations where pip can avoid executing a Turing complete "configuration" file, without impeding the eventual adoption of a more comprehensive solution.</p><p dir="ltr" class="">I don't think that needs a PEP - just an RFE against pip to make it d2to1 aware for each use case where it's relevant, like installing setup.py dependencies. (And perhaps a similar RFE against setuptools)</p><p dir="ltr" class="">Projects that choose to rely on that new feature will be setting a high minimum installer version for their users, but some projects will be OK with that (especially projects private to a single organisation after upgrading pip on their production systems).</p><p dir="ltr" class="">Cheers,<br class="">
Nick.</p><div class=""><br class=""></div>
</div></blockquote><br class=""></div><div>I don’t think that’s going to work, because if you only make pip aware of it then you break ``python setup.py sdist``, if you make setuptools aware of it then you don’t need pip to be aware of it because we’ll get it for free from setuptools being aware of it.</div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">---</div><div class="">Donald Stufft</div><div class="">PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA</div></div></div>
</div>
<br class=""></body></html>