-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On behalf of the Python development team, I'm happy to announce the
second beta preview release of Python 3.2.
Python 3.2 is a continuation of the efforts to improve and stabilize the
Python 3.x line. Since the final release of Python 2.7, the 2.x line
will only receive bugfixes, and new features are developed for 3.x only.
Since PEP 3003, the Moratorium on Language Changes, is in effect, there
are no changes in Python's syntax and built-in types in Python 3.2.
Development efforts concentrated on the standard library and support for
porting code to Python 3. Highlights are:
* numerous improvements to the unittest module
* PEP 3147, support for .pyc repository directories
* PEP 3149, support for version tagged dynamic libraries
* PEP 3148, a new futures library for concurrent programming
* PEP 384, a stable ABI for extension modules
* PEP 391, dictionary-based logging configuration
* an overhauled GIL implementation that reduces contention
* an extended email package that handles bytes messages
* countless fixes regarding bytes/string issues; among them full
support for a bytes environment (filenames, environment variables)
* many consistency and behavior fixes for numeric operations
* a sysconfig module to access configuration information
* a pure-Python implementation of the datetime module
* additions to the shutil module, among them archive file support
* improvements to pdb, the Python debugger
For a more extensive list of changes in 3.2, see
http://docs.python.org/3.2/whatsnew/3.2.html
To download Python 3.2 visit:
http://www.python.org/download/releases/3.2/
Please consider trying Python 3.2 with your code and reporting any bugs
you may notice to:
http://bugs.python.org/
Enjoy!
- --
Georg Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.2's contributors)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk0Q/aAACgkQN9GcIYhpnLDf8gCgkLGAsE+T3R505jZc1RxXDYsa
NSsAnRGaFjeTm9o2Z5O8FuIzTUG8t1PT
=hHzz
-----END PGP SIGNATURE-----
Hi,
it's now time for beta2; you know the drill by now: I'll be in
#python-dev on and off, if you like to commit something please
coordinate there.
Georg
I would like to commit a couple of new feature patches in the next
couple of days for #9299 (if no one else does it) and #10534 (working on
that). It appears to be somewhat customary to follow such patches with
3.1/2.7 blocks, but Georg implied in another message that the process is
obsolete in that no one is doing blind mass merges anymore, and I
apparently cannot do blocks with TortoiseSvn. So is it alright if I make
the commits and simply note in the commit messages that they are for a
new feature and should not be merged backwards?
--
Terry Jan Reedy
Hi,
I wonder if it's still necessary to provide .tar.bz2 and .tgz source
tarballs. If anything, it would be nice to provide .tar.xz in addition
to .tar.bz2, which has a nicer compression ratio:
.tgz - 13 MB
.tar.bz2 - 11 MB
.tar.xz - 8.6 MB
Georg
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On behalf of the Python development team, I'm happy to announce the
first of two beta preview releases of Python 3.2.
Python 3.2 is a continuation of the efforts to improve and stabilize the
Python 3.x line. Since the final release of Python 2.7, the 2.x line
will only receive bugfixes, and new features are developed for 3.x only.
Since PEP 3003, the Moratorium on Language Changes, is in effect, there
are no changes in Python's syntax and built-in types in Python 3.2.
Development efforts concentrated on the standard library and support for
porting code to Python 3. Highlights are:
* numerous improvements to the unittest module
* PEP 3147, support for .pyc repository directories
* PEP 3149, support for version tagged dynamic libraries
* PEP 3148, a new futures library for concurrent programming
* PEP 384, a stable ABI for extension modules
* PEP 391, dictionary-based logging configuration
* an overhauled GIL implementation that reduces contention
* an extended email package that handles bytes messages
* countless fixes regarding bytes/string issues; among them full
support for a bytes environment (filenames, environment variables)
* many consistency and behavior fixes for numeric operations
* a sysconfig module to access configuration information
* a pure-Python implementation of the datetime module
* additions to the shutil module, among them archive file support
* improvements to pdb, the Python debugger
For a more extensive list of changes in 3.2, see
http://docs.python.org/3.2/whatsnew/3.2.html
To download Python 3.2 visit:
http://www.python.org/download/releases/3.2/
Please consider trying Python 3.2 with your code and reporting any bugs
you may notice to:
http://bugs.python.org/
Enjoy!
- --
Georg Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.2's contributors)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iEYEARECAAYFAkz9WcgACgkQN9GcIYhpnLBRYwCeMmH1GMmKOx9fVk8a/F0/TOzj
Vp0AoIHYBNcxV/U0AXIwMGWFHi1bAB+a
=KBam
-----END PGP SIGNATURE-----
Hi,
after careful discussion I have come to the conclusion it is
not feasible to get the migration done in time for 3.2 final,
especially considering that December is not exactly a time
where everyone wants to be doing extra work.
All releases up and including 3.2 will therefore be made from SVN.
3.2 will face the same small issue as 2.7 and 3.1, i.e. that
subsequent releases will have different-looking build identification.
Dirkjan is positive that he will have the test repo ready by the
end of the month. That means that if the issues left in the test
repo are small enough to be done in a few days, SVN will be frozen
as soon as 3.2 final is out of the door, and anything committed
to py3k from then on will go to Mercurial once it's ready.
I hope this is a good compromise for everyone.
Georg
