Terry Reedy wrote: > [snip...] >> >> I don't think that's a novel idea though - I'm pretty sure it was >> suggested (and met with general approval) when the idea of a short >> release cycle for 3.1 was first brought up. > > I presume because it has been stated before. > > In addition to the question above, I am also trying to provoke thought > on the nature and purpose of 2.7. Backporting features 'if someone > feels like it' seems pretty haphazard. For someone wanting to > maintain compatibility across multiple 2.x releases, a random new > features may be nearly useless. > The "What's new in Python 2.7" list is already very impressive. :-) Michael > Terry Jan Reedy > > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk > -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4