On Fri, Sep 12, 2008 at 7:54 AM, Barry Warsaw <barry at python.org> wrote: > We had a lot of discussion recently about changing the release schedule and > splitting Python 2.6 and 3.0. There was general consensus that this was a > good idea, in order to hit our October 1 deadline for Python 2.6 final at > least. Does it matter to anyone besides the you, the Python developers, whether the schedule slips by two weeks, or two months, for that matter? I am underwhelmed by 3.0 b3: sax and 2to3 are/were broken. A b4 release for 3.0 (at least) would seem more prudent. Edward
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