I've built and tested the latest py3k from scratch on Ubuntu, Fedora 7, OSX 10.4 and OSX 10.5, and found no issues. So the code freeze is a fact. Don't check anything into the py3k branch unless I tell you to. Please file high-priority bugs and assign them to me if you think you've found a showstopper. The buildbot is green for Solaris also, so I think we're in good shape. I don't see any green buildbots for Windows though, but Windows is always a flakey situation; Christian, what's your assessment? I see a few tests leaking; in particular test_ssl (1522 refs leaned per run!) and test_urllib2_localnet (3 per run). Anyone interested in researching these feel free to do so; just upload a patch and file a bug if you've squashed the leaks (or some). We're on for a 3.0a2 release Friday! --Guido On Dec 5, 2007 5:46 PM, Guido van Rossum <guido at python.org> wrote: > I'm planning to freeze the py3k branch in 2-3 hours, some time > after/around 8pm PST (midnight UTC). > > If someone wants to do another svnmerge from the trunk please do it > before then -- though we're nearly current so I don't mind not having > the last few changes merged into this release (it's only Raymond's > refactoring of __length_hint__ implementations). > > If there's anything you think really should be in this release, please > speak up ASAP. Filing a high priority bug and assigning it to me would > be a great way to get my attention. > > -- > --Guido van Rossum (home page: http://www.python.org/~guido/) > -- --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