Re: [Python-Dev] Py3k code freeze imminent; 3.0a2 release Friday

2007-12-07 Thread Guido van Rossum
As people have been disregarding the freeze anyway, I declare the py3k branch back open. I tagged it with r30a2 yesterday morning and that's the version that I'll be releasing shortly (waiting for Crys & me to sort out some things around the Windows MSI installer). --Guido On Dec 5, 2007 8:43 PM,

Re: [Python-Dev] Py3k code freeze imminent; 3.0a2 release Friday

2007-12-06 Thread Bill Janssen
> I see a few tests leaking; in particular test_ssl (1522 refs leaned > per run!) I'm looking at this, but I haven't found anything in the last week... Bill ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python

Re: [Python-Dev] Py3k code freeze imminent; 3.0a2 release Friday

2007-12-06 Thread Christian Heimes
Guido van Rossum wrote: > 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). I see the refer

Re: [Python-Dev] Py3k code freeze imminent; 3.0a2 release Friday

2007-12-06 Thread Christian Heimes
Guido van Rossum wrote: > 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? test_mailbox is still failing with lots of errors. The module needs

Re: [Python-Dev] Py3k code freeze imminent; 3.0a2 release Friday

2007-12-05 Thread Guido van Rossum
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 showsto

[Python-Dev] Py3k code freeze imminent; 3.0a2 release Friday

2007-12-05 Thread Guido van Rossum
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 Ray