<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 Jan 25, 2017, at 2:11 PM, Paul Moore <<a href="mailto:p.f.moore@gmail.com" class="">p.f.moore@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 25 January 2017 at 17:20, Chris Withers <<a href="mailto:chris@simplistix.co.uk" class="">chris@simplistix.co.uk</a>> wrote:<br class=""><blockquote type="cite" class="">Right, so what's the recommended one-step way to set up a virtualenv now in<br class="">Py 2.6-3.6?<br class=""></blockquote><br class="">This is the point I would consider most significant here. Virtualenv<br class="">is deliberately built to allow use offline - pip, wheel and setuptools<br class="">are bundled so that it's possible to create a virtualenv without<br class="">needing Internet access. This change to setuptools will, if I<br class="">understand it, break that expectation.<br class=""><br class="">While it's not a common scenario, I think it's something that should<br class="">be considered. Going forward, I see a number of options for<br class="">virtualenv:<br class=""><br class="">1. Bundle all of setuptools' dependencies as well.<br class="">2. Drop the "no internet required" constraint - if we do this, it may<br class="">be reasonable to only bundle pip, and get latest versions of<br class="">everything else from PyPI.<br class="">3. Drop auto-installing setuptools (it's not needed unless you're<br class="">installing from sdist, and it's only a "pip install setuptools" away<br class="">for people who need it).<br class="">4. Document the changed behaviour by saying that no internet is<br class="">required as long as you use --no-setuptools.<br class=""><br class="">Thoughts, anyone? Is the situation common enough to warrant anything<br class="">other than (4)? It used to be for me, when pip didn't cache downloads<br class="">and I had a secured proxy to deal with, but now I'd be OK with (4).<br class=""><br class=""></div></div></blockquote><br class=""></div><div>If we get PEP 518 landed in pip I think that (3) is the right step forward.</div><div class=""><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class="">—<br class="">Donald Stufft<br class=""></div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""></body></html>