<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 Sep 15, 2013, at 3:56 PM, Alex Burke <<a href="mailto:alexjeffburke@gmail.com">alexjeffburke@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Sunday, 15 September 2013, Donald Stufft wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So there've been a number of updates to PEP453, so i'm posting it here again for more discussion:<br>
<br>
Viewable online at: <a href="http://www.python.org/dev/peps/pep-0453/" target="_blank">http://www.python.org/dev/peps/pep-0453/</a><br>
<br>
<snip PEP text></blockquote><div><br></div><div>Hey,</div><div><br></div><div>I've been trying hard to follow the discussions but please forgive this question if its has been hashed out already.</div><div><br></div>
<div>I was a little concerned, despite it being an implementation detail, about bundling a pip which ends up being present somewhere whwerever the bootstrap is.</div><div><br></div><div>I know the concept of a mini-pip has been abandoned, but I couldn't help thinking about the <span style="">pip / setuptools as wheels in</span> Nick's roadmap summary. Instead of a copy of pip, could there not be minimal code to simply fetch the wheel and install that or perhaps even use it directly (a la what was possible with eggs)?</div>
<div><br></div><div>Perhaps that is already too much code and there are good reasons not to do this, but hoped asking would make it clear.</div><div><br></div><div>Thanks, Alex J Burke.</div><div></div>
</blockquote></div><br><div>Basically three reasons:</div><div> - There's a lot of code to handle a variety of situations in pip, it would</div><div> be much harder to extract this code and keep it up to date in a way</div><div> that the "mini pip" could use it. It would also not be as battle worn as</div><div> the pip code.</div><div> - On top of the one time cost there is the ongoing cost. As the packaging</div><div> ecosystem progresses the stdlib implementation will need to be kept</div><div> up to date as well as the pip code.</div><div> - We need to include a copy of pip in order to support offline installs either</div><div> way. Since we have the private copy there to support offline we might as</div><div> well use it to handle everything.</div><div>
<br>-----------------<br>Donald Stufft<br>PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
</div>
<br></body></html>