> > In any schedule, there likely would be a month between a1 and a2, so > > the release of Python 2.3a1 would simultaneously be a last call for > > great new features. Between a1 and c1, there would be four months, > > giving plenty of time (IMO) for bug fixes. > > If I interpret the above correctly, then for my typical patches it seems > like I would have to at least b1 (and possibly c1) to submit them for > consideration. Is my interpretation correct? I don't know what your "typical patches" are. Why do you expect they need to be submitted after b1? After c1 would suggest they are too late! --Guido van Rossum (home page: http://www.python.org/~guido/)
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