Now that 2.6.9 is out, I wonder if there's anything we can or should do to the
Mercurial repository to explicitly prevent commits to the 2.6 branch? We have
we done to older branches?
Also, can anybody think of anything in the devguide that needs to be updated?
-----BEGIN PGP SIGNED MESSAGE-----
On behalf of the Python development team, I'm quite happy to announce the
Python 3.3.3 release candidate 1.
Python 3.3.3 includes several security fixes and over 150 bug fixes compared to
the Python 3.3.2 release.
This release fully supports OS X 10.9 Mavericks. In particular, this release
fixes an issue that could cause previous versions of Python to crash when typing
in interactive mode on OS X 10.9.
Python 3.3.3 also contains a new batteries-included feature for OS X users of
IDLE and other Tkinter-based programs. The python.org Mac OS X 64-bit/32-bit
x86-64/i386 Installer for OS X 10.6+ now includes its own builtin version of
Tcl/Tk 8.5. It is no longer necessary to install a third-party version of
Tcl/Tk 8.5 to workaround the problematic system versions. See
http://www.python.org/download/mac/tcltk/ for more information.
Python 3.3 includes a range of improvements of the 3.x series, as well as easier
porting between 2.x and 3.x. In total, almost 500 API items are new or improved
in Python 3.3. For a more extensive list of changes in the 3.3 series, see
and for the detailed changelog of 3.3.3, see
To download Python 3.3.3 rc1 visit:
This is a preview release, please report any bugs to
The final version is scheduled to be released in two weeks' time, on or about
the 10th of November.
Georg Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.3's contributors)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
-----END PGP SIGNATURE-----
I've tagged 3.3.3rc1 today; final is scheduled for Nov 8. Please notify
me of any 3.3 regressions you find; I will then port them to the repo
from which the final is cut.
General bugfixing can continue on the 3.3 branch in the main repo and will
not be relevant for 3.3.
On Thu, 24 Oct 2013 10:12:07 -0400, Brett Cannon <brett(a)yvrsfo.ca> wrote:
> FYI if you didn't know
You mean disk space? I don't get notified automatically when /tmp fills
up with test detritus. I suppose I should set something up.
However, it looks like someone has added some tests that use more tmp space,
since the amount of /tmp that exist has been fine up until this point,
and the runs on 2.7 and 3.3 are still working.
I can increase /tmp, but I wonder if there is a new test that should
be protected with the largefile resource. Perhaps not,
/tmp is currently 16MB on those bots, and I'm not sure what we
consider 'large' for test files.
With PEP 453 accepted, could Donald please be upgraded to full
committer access for ensurepip maintenance (the initial PEP 453
commits will still go through review on the tracker). (His SSH key is
already on file for PEP updates, so I believe the only actual change
needed is to adjust his status on the issue tracker)
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
This is a reminder that Python 2.6.9 final - and by that I mean *really* final
as it will be the last supported version of Python 2.6 - is scheduled for
release one week from today, on October 28, 2013.
All known showstopper security bugs have been applied to the branch. If you
know of anything that should go into Python 2.6 but has not yet, please
contact me asap. Please test rc1 on your platforms and code, and let me know
if you have any problems.
Barring any showstoppers, I will likely cut the release AM my local time.
On behalf of the Python development team, I'm very pleased to announce
the fourth and final alpha release of Python 3.4.
This is a preview release, and its use is not recommended for
Python 3.4 includes a range of improvements of the 3.x series, including
hundreds of small improvements and bug fixes. Major new features and
changes in the 3.4 release series so far include:
* PEP 435, a standardized "enum" module
* PEP 436, a build enhancement that will help generate introspection
information for builtins
* PEP 442, improved semantics for object finalization
* PEP 443, adding single-dispatch generic functions to the standard library
* PEP 445, a new C API for implementing custom memory allocators
* PEP 446, changing file descriptors to not be inherited by default
* PEP 450, the new "statistics" module
* PEP 3156, the new "asyncio" module, a new framework for asynchronous I/O
To download Python 3.4.0a4 visit:
Python 3.4.0a4 has several known issues:
* The Python compiler has a small memory leak.
* The "asyncio" module test suite fails on some platforms.
* I/O conducted by the "asyncio" module may, rarely,
erroneously time out. The timeout takes one hour.
Please consider trying Python 3.4.0a4 with your code and reporting any
new issues you notice to:
Larry Hastings, Release Manager
larry at hastings.org
(on behalf of the entire python-dev team and 3.4's contributors)
3.4.0a4 is tagged and I'm in the process of releasing it. But it's
going to be, let's say, more "alpha-quality" than the previous alphas.
* There's a reference count leak in the compiler.
* asyncio test suite sometimes times out, which takes... an hour.
* asyncio test suit fails on a couple of platforms.
I don't think any of these are bad enough to slip the schedule. However,
if you disagree, pipe up, feel free to try and change my mind, it's not
A lot has landed in trunk in the last day or two: Tulip, Argument
Clinic, and statistics just landed too. The buildbots are upset at us
humans--there's a lot of red. See for yourself:
I'd like to tag Alpha 4 late tonight, but if the buildbots are still
mostly-red it's a bad idea. If you can help make the buildbots happy,
and have some time in the next eight or ten hours, please hop in to
#python-dev and ask what you can do to help.
SOS -- Save Our Schedule,