<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 13, 2013, at 11:05 AM, Tres Seaver <<a href="mailto:tseaver@palladion.com">tseaver@palladion.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><fieldset style="padding-top:10px; border:0px; border: 3px solid #CCC; padding-left: 20px;"><legend style="font-weight:bold">Signed PGP part</legend><div style="padding-left:3px;">On 07/13/2013 08:25 AM, Nick Coghlan wrote:<br>> I think we need to flip the dependencies so that pip as the installer<br>> has all the essential code for installation from PyPI and then<br>> setuptools and distlib depend on that pip infrastructure. No need to<br>> add anything to the standard library prematurely when we can add it to<br>> pip instead.<br><br>- -1.<span class="Apple-converted-space"> </span> That would effectively mean inlining the bulk of setuptools' code<br>into pip (which is just a UI / policy shim over it).<span class="Apple-converted-space"> </span> You might as well<br>just have your bootstrapper install both pip and setuptools and be done<br><br>Unless distlib (or something like it) lands in the stdlib with enough<br>features to support a setuptools-less pip, of course.<br><br>At-which-point-the-State-will-wither-away'ly,<br><br><br>Tres.<br>- -- <br>===================================================================<br>Tres Seaver<span class="Apple-converted-space"> </span> <span class="Apple-converted-space"> </span> <span class="Apple-converted-space"> </span> <span class="Apple-converted-space"> </span> <span class="Apple-converted-space"> </span> +1 540-429-0999<span class="Apple-converted-space"> </span> <span class="Apple-converted-space"> </span> <span class="Apple-converted-space"> </span> <span class="Apple-converted-space"> </span> <span class="Apple-converted-space"> </span> <a href="mailto:tseaver@palladion.com">tseaver@palladion.com</a><br>Palladion Software<span class="Apple-converted-space"> </span> "Excellence by Design"<span class="Apple-converted-space"> </span> <span class="Apple-converted-space"> </span> <a href="http://palladion.com">http://palladion.com</a><br></div></fieldset><br><br>_______________________________________________<br>Distutils-SIG maillist<span class="Apple-converted-space"> </span> -<span class="Apple-converted-space"> </span> <a href="mailto:Distutils-SIG@python.org">Distutils-SIG@python.org</a><br><a href="http://mail.python.org/mailman/listinfo/distutils-sig">http://mail.python.org/mailman/listinfo/distutils-sig</a><br></blockquote></div><br><div>I was planning on doing this to pip anyways. pip should not have any dependencies setuptools or otherwise. So regardless of what happens with this PEP I want pip to be inlining setuptools and providing the code to make that transparent during install. This would mean that for people who are _just_ installing packages they don't need setuptools installed.</div><div>
<br>-----------------<br>Donald Stufft<br>PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
</div>
<br></body></html>