On Tue, Jan 27, 2009 at 3:19 PM, Raymond Hettinger <python at rcn.com> wrote: > If 3.1 goes out right away, then it doesn't matter if 3.0 looks ridiculous. > All eyes go to the latest release. Better to get this done before more > people download 3.0 to kick the tires. It seems like we are arguing over the version number of basically the same thing. I would like to see 3.0.1 released in early February for nearly the reasons you name. However, it seems to me that there are two kinds of issues: those like __cmp__ removal and some silly IO bugs that have been fixed for a while and our waiting to be released. There's also projects like io in c which are important, but would not make the schedule you and I want for 3.0.1/3.1. It's for those longer term features that I want 3.0.1 and 3.1. If we immedatly released 3.1, when would those longer term projects that are important for migration make it to stable? 3.2 is probably a while off. -- Regards, Benjamin
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