[Python-Dev] Releasing beta 3's tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pending a resolution of bug 3611 (which has an attached patch that we're testing now), I plan on releasing 2.6 and 3.0 beta 3 tonight. Please do not make any commits to the trees unless you ask me first, until further notice. I am on #python-dev if you need an immediate decision. Thanks. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSKyecnEjvBPtnXfVAQJ4DgQAg7hNzp76nUT8/dA4C2xTqwL+mmtXeu2s MLbez1xVk3IoU3J/GRRcposaUQKoPToophndj1yk57v/g/AtrXIAjFRXkqH7giU5 eD7WltOt3Ch/f6ZBkT9eHttq9uaQB35kKcCPNUSL81C24xn8z7JS08KG+6bgx1hE g0tYCMAj7Wk= =tomA -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Python 2.6 on AMD64 recusion crash
While looking at 2.6 for Windows, I've found a recursion related crash in test_cpickle on 64bit builds. Specifically, the 'cPickleDeepRecursive' is causing a stack overflow, and the debugger tells me the actual recursion depth was 629 at the crash. The reason the 64bit build doesn't see more crashes is apparently due to another regression in 2.6 - http://bugs.python.org/issue3373. It appears that in some cases, the recursion counter is actually incremented *twice* for each entry, thereby causing the maximum recursion depth exceeded exception to appear at a true recusion limit of 500. However, test_cpickle takes a different path and doesn't see this doubling of the count - therefore dieing at the depth of 629 that I can see. My solution to this was to simply double the stack size for the executables in 64bit builds, from 2MB to 4MB (2.1 and 4.2 for debug builds.) Is this an appropriate fix? Cheers, Mark ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] RELEASED Python 2.6b3 and 3.0b3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On behalf of the Python development team and the Python community, I am happy to announce the third and last planned beta releases of Python 2.6 and Python 3.0. Please note that these are beta releases, and as such are not suitable for production environments. We continue to strive for a high degree of quality, and these releases are intended to freeze the feature set for Python 2.6 and 3.0. As these are the last planned beta releases, we strongly urge you to download these releases and test them against your code. Once we reach release candidates (currently planned for 03-Sep-2008), only highly critical bugs will be fixed before the final release. If you find things broken or incorrect, please submit bug reports at http://bugs.python.org For more information and downloadable distributions, see the Python 2.6 website: http://www.python.org/download/releases/2.6/ and the Python 3.0 web site: http://www.python.org/download/releases/3.0/ See PEP 361 for release schedule details: http://www.python.org/dev/peps/pep-0361/ Enjoy, - -Barry Barry Warsaw [EMAIL PROTECTED] Python 2.6/3.0 Release Manager (on behalf of the entire python-dev team) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIrN472YZpQepbvXERAl4fAJ9QxHhSn/jYdA3lCYvgfXRhBVV2pgCfdNUx 3NTlSrsSULxXhoMqiNmUMSg= =Z4+y -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2.6 on Windows
Can anybody verify and hopefully fix the problems seen in the Windows bots for the trunk (i.e. 2.6)? FWIW, I can't reproduce most of those problems. My 32bit build sees: 303 tests OK. 57 tests skipped: test__locale test_aepack test_al test_applesingle test_bsddb185 test_bsddb3 test_cd test_cl test_codecmaps_cn test_codecmaps_hk test_codecmaps_jp test_codecmaps_kr test_codecmaps_tw test_commands test_crypt test_curses test_dbm test_dl test_epoll test_fcntl test_fork1 test_gdbm test_gl test_grp test_imageop test_imgfile test_ioctl test_kqueue test_largefile test_linuxaudiodev test_macos test_macostools test_mhlib test_nis test_normalization test_openpty test_ossaudiodev test_pipes test_poll test_posix test_pty test_pwd test_py3kwarn test_resource test_scriptpackages test_signal test_socketserver test_ssl test_sunaudiodev test_tcl test_threadsignals test_timeout test_urllib2net test_urllibnet test_wait3 test_wait4 test_zipfile64 2 skips unexpected on win32: test_tcl test_ssl and once I made the changes I just uploaded to http://bugs.python.org/issue3625 (which are just tweaks to skip certain tests on win64), a 64bit build reports: 303 tests OK. 57 tests skipped: test__locale test_aepack test_al test_applesingle test_bsddb185 test_bsddb3 test_cd test_cl test_codecmaps_cn test_codecmaps_hk test_codecmaps_jp test_codecmaps_kr test_codecmaps_tw test_commands test_crypt test_curses test_dbm test_dl test_epoll test_fcntl test_fork1 test_gdbm test_gl test_grp test_imageop test_imgfile test_ioctl test_kqueue test_largefile test_linuxaudiodev test_macos test_macostools test_mhlib test_nis test_normalization test_openpty test_ossaudiodev test_pipes test_poll test_posix test_pty test_pwd test_py3kwarn test_resource test_scriptpackages test_signal test_socketserver test_ssl test_sunaudiodev test_tcl test_threadsignals test_timeout test_urllib2net test_urllibnet test_wait3 test_wait4 test_zipfile64 2 skips unexpected on win32: test_tcl test_ssl Which is the best state I've ever managed to get the 64bit build to. Note however that bsddb3 was skipped by my tests. Running that test alone, both platforms report the same error as the buildbot: FAIL: test01_basic_replication (bsddb.test.test_replication.DBReplicationManager) -- Traceback (most recent call last): File o:\src\python-svn-amd64\lib\bsddb\test\test_replication.py, line 134, in test01_basic_replication self.assertTrue(time.time()timeout) AssertionError However, the error appears after a number of seconds of inactivity - so I suspect it has nothing to do with the timer resolution on Windows and more about the fact that the test really did fail. So while I'm not sure what else the buildbot is seeing, the only real problem seems exactly 1 test in the bsddb3 tests. Cheers, Mark ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
