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 extra embracement and love on Windows. Most to all of the problems are related to the newline separator \r\n. Some modules are also failing when I run a refleak regression test, see http://bugs.python.org/issue1540 I've ironed out the last cosmetic problems in the PCbuild9 directory and profile guided optimization builds. A PGO version can be build with "build_pgo -2" (runs the complete unit test suite) or "build_pgo" (runs PyBench) in a VS 2008 command shell. The x64 builds are looking fine except of tkinter (it doesn't build) but I'm not able to test the x64 version on my computer. Could you please add two comments to the release notes for Windows users? * On Windows Python can't be run from a directory with non ASCII chars in its path name. #1342 * The current releases of MinGW and Cygwin can't build Python extensions since they don't support msvcr90.dll. The necessary bits and pieces are already in Python and cygwin cvs.

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).

The test_ssl tests are only leaking with the -unetwork option. On my Ubuntu box they are leaking 1536 references per turn. For heaven's sake I can't remember how I found the leaking code lines the last time. Py_DUMP_REFS dumps too many information. Christian

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

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, Guido van Rossum wrote:

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 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/)

-- --Guido van Rossum (home page: http://www.python.org/~guido/)