On Thu, Oct 28, 2010 at 9:04 AM, Barry Warsaw <span dir="ltr"><<a href="mailto:barry@python.org">barry@python.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Who is the target audience for a Python 2.8? What exactly would a Python 2.8<br>
accomplish?<br>
<br>
If Python 2.8 doesn't include new features, well, then what's the point?<br>
Python 2.7 will be bug fix maintained for a long time, longer in fact than<br>
previous Python 2 versions. So a no-feature Python 2.8 can't be about<br>
improving Python 2 stability over time (i.e. just fix the bug in Python 2.7).<br>
<br>
If Python 2.8 is about adding new features, then it has to be about<br>
backporting those features from Python 3. Adding new feature only to a Python<br>
2.8 *isn't* Python, it's a fork of Python.</blockquote><div><br>Thinking about language features and core type this seems reasonable, but with the standard library this seems less reasonable -- there's lots of conservative changes to the standard library which aren't bug fixes, and the more the standard library is out of sync between Python 2 and 3 the harder maintaining software that works across those versions becomes.<br>
<br>Though one opportunity is to distribute modules from the standard library under new names (e.g., unittest2), and at least in Python 2 you don't have to do anything fancy or worry about the standard library has catching up to the standard library forked module.<br>
<br>Library installers seem particularly apropos to this discussion, as everyone seems excited to get them into the standard library and distributed with Python, but with the current plan that will never happen with Python 2.<br>
<br></div></div>-- <br>Ian Bicking | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br>