Thomas Heller writes: > Will the release candidate have the same version number as the final > version? The typical case has been that the candidate has a distinct version number. I think 2.3.1 has taught us to be very careful, so we should keep the distinction between the candidate and the actual release. My opinion: What's "candidate" isn't the actual file we post to python.org, but the bits in CVS that form the implementation and build process. The actual packages are a byproduct of that. > > I don't know if the RC needs a windows installer built, as the problems > > are in non-windows platforms. > > I don't mind building one. I think there should be one. They've paid off in the past. I'm planning to post the 2.3.2c1 documentation late Sunday night or early Monday morning. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation
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