On Mon, Dec 6, 2010 at 13:46, Georg Brandl wrote:
> -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 t
-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
Please remember, no new features from this point on :)
Georg
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
Am 06.12.2010 13:24, schrieb Barry Warsaw:
I can't imagine *adding* a download format is that much more complex, except
perhaps for our users to try to figure out which file to grab, and even that's
stretching it I think. But I would be okay with adding an .xz download for
3.2 and then re-evalua
Am 06.12.2010 13:24, schrieb Barry Warsaw:
> On Dec 05, 2010, at 11:15 PM, Brett Cannon wrote:
>
>>It only increases complexity if we don't cut one of the tar.bz2 or tgz
>>source releases. But by offering a a tar.xz file we can give people a
>>smaller download which saves everyone time and bandwid
On Dec 05, 2010, at 11:15 PM, Brett Cannon wrote:
>It only increases complexity if we don't cut one of the tar.bz2 or tgz
>source releases. But by offering a a tar.xz file we can give people a
>smaller download which saves everyone time and bandwidth which can
>matter if the downloader's Internet
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.
