<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Mar 22, 2014, at 9:17 PM, Ben Darnell <<a href="mailto:ben@bendarnell.com">ben@bendarnell.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Mar 22, 2014 at 8:55 PM, Nick Coghlan <span dir="ltr"><<a href="mailto:ncoghlan@gmail.com" target="_blank">ncoghlan@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">What we have essentially found is that where we could basically get<br></div>
away with an 18 month update cycle for improved network security<br>
support (extended out to a few years by certain major platform<br>
vendors), that approach *isn't* working when it comes to putting a<br>
feature release into long term maintenance mode. I don't think the<br>
situation isn't critical yet, but it's getting close, and I think we<br>
need to deal with it within the 12 months (and preferably sooner than<br>
that).<br></blockquote><div><br></div><div>This PEP as written applies to both Python 2.x and 3.x, but the two situations are very different. 3.x is on a ~18 month update cycle, so why isn't the status quo acceptable there? Python 2.x has less than 18 months of support left, so could it get by with a single exceptional release instead of a general relaxing of the rules? (if it were up to me, I'd call that release Python 2.8 instead of 2.7.7) If this PEP is mainly about a one-shot update to the security components of Python 2.x, I'd like to see an explicit list of what is in scope for the update.</div>
<div><br></div><div>-Ben</div></div></div></div>
_______________________________________________<br>Python-Dev mailing list<br><a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a><br>https://mail.python.org/mailman/listinfo/python-dev<br>Unsubscribe: https://mail.python.org/mailman/options/python-dev/donald%40stufft.io<br></blockquote></div><br><div>As one of the instigators who convinced Nick to write this PEP I’m far less concerned</div><div>about back porting things to earlier 3.x releases than I am about getting things into</div><div>2.7 at this point. Going from 3.2 to 3.4 is not terribly difficult if it requires any work at</div><div>all. Going from 2.7 to 3.4 is often times a significant investment in resources that has</div><div>to be taken by *every* network using project.</div><div>
<br>-----------------<br>Donald Stufft<br>PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
</div>
<br></body></html>