<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 May 15, 2014, at 7:34 AM, Nick Coghlan <<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p dir="ltr"><br>
On 15 May 2014 21:20, "Donald Stufft" <<a href="mailto:donald@stufft.io">donald@stufft.io</a>> wrote:<br>
><br>
><br>
> On May 15, 2014, at 4:16 AM, Daniele Sluijters <<a href="mailto:daniele.sluijters@gmail.com">daniele.sluijters@gmail.com</a>> wrote:<br>
><br>
> > Has anyone considered what this will mean for people on distributions<br>
> > that ship older pip versions that can't be upgraded outside of the<br>
> > release cycle (like Debian and Redhat)?<br>
> ><br>
><br>
> So a nice property of this, is that degrades gracefully. The things we need in<br>
> the installer to actually make the core functionality (specifying additional<br>
> locations) work has existed for a very long time. The piece of the<br>
> functionality that they'd be missing is the UX around discovering the<br>
> additional index. We could/should probably also indicate this location on the<br>
> PyPI project page so that would help with this some.</p><p dir="ltr">I was more thinking of automated use cases that are currently working, but would need to switch command line options or config settings for the change described in the PEP.</p><p dir="ltr">We'll want to take that into account when deciding how long to make the server half of the deprecation period for existing externally hosted projects.</p><div><br></div></blockquote><br></div><div><div>Yea sure. I just picked a timeline. There's no science or logic behind it other</div><div>then it seemed like a reasonably long time. It can be adjusted to suit our</div><div>tastes.</div><div><br></div><div>I was just making sure that it was clear that this wasn't going to be a change</div><div>that made it impossible for older versions of the tools to download files and</div><div>that the older tools would primarily be affected in that the UI around</div><div>discovering the additional locations is where they would affected, not the</div><div>ability to actually install something.</div><div><br></div><div>I mean, even if someone is on the absolute latest version of the tooling this</div><div>is going to be a change that is breaking for some ~7% of projects in some</div><div>fashion, although for a large chunk of them only for specific older versions.</div><div>So the lifecycle of LTS versions of Linux only really matter in the discovering</div><div>of additional URLs to add.</div></div><br><div>
<br>-----------------<br>Donald Stufft<br>PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
</div>
<br></body></html>