I remember earlier discussion on the Python 2.1 release schedule, and never managed to comment on those. I believe that Python contributors and maintainers did an enourmous job in releasing Python 2, which took quite some time from everybody's life. I think it is unrealistic to expect the same amount of commitment for the next release, especially if that release appears just a few months after the previous release (that is, one month from now). So I'd like to ask the release manager to take that into account. I'm not quite sure what kind of action I expect; possible alternatives are: - declare 2.1 a pure bug fix release only; with a minimal set of new features. In particular, don't push for completion of PEPs; everybody should then accept that most features that are currently discussed will appear in Python 2.2. - move the schedule for Python 2.1 back (or is it forward?) by, say, a few month. This will people give some time to do the things that did not get the right amount of attention during 2.0 release, and will still allow to work on new and interesting features. Just my 0.02EUR, Martin
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