> Then this is a good time to ask what strategy will be followed > post-2.0. Do you want a moratorium on massive checkins for a time > while 2.0 shakes out, re-opening the tree for larger changes in a few > months? Or will you try to live with a CVS branch for 2.0 and re-open > the tree immediately? If we need to issue a patch release, we'll use a branch. That seems the only reasonable approach. The tree will be open for checkins as soon as 2.0 is released (tonight is looking good!), but I hope the people exercise some restraint and discuss their plans for significant checkins on the python-dev list first. A lot of things should probably be discussed in the form of PEPs too! --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