On behalf of the Python development team, I'm happy to announce the first alpha release of Python 3.3.0. This is a preview release, and its use is not recommended in production settings. Python 3.3 includes a range of improvements of the 3.x series, as well as easier porting between 2.x and 3.x. Major new features in the 3.3 release series are: * PEP 380, Syntax for Delegating to a Subgenerator ("yield from") * PEP 393, Flexible String Representation (doing away with the distinction between "wide" and "narrow" Unicode builds) * PEP 409, Suppressing Exception Context * PEP 3151, Reworking the OS and IO exception hierarchy * The new "packaging" module, building upon the "distribute" and "distutils2" projects and deprecating "distutils" * The new "lzma" module with LZMA/XZ support * PEP 3155, Qualified name for classes and functions * PEP 414, explicit Unicode literals to help with porting * The new "faulthandler" module that helps diagnosing crashes * Wrappers for many more POSIX functions in the "os" and "signal" modules, as well as other useful functions such as "sendfile()" For a more extensive list of changes in 3.3.0, see http://docs.python.org/3.3/whatsnew/3.3.html To download Python 3.3.0 visit: http://www.python.org/download/releases/3.3.0/ Please consider trying Python 3.3.0a1 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.3's contributors)
Could we remove the f_yieldfrom attribute from frameobject (at the Python level) before it is too late and we are stuck with it. Issue (with patch) here: http://bugs.python.org/issue13970 Cheers, Mark.
On 3/5/2012 2:54 AM, Georg Brandl wrote:
On behalf of the Python development team, I'm happy to announce the first alpha release of Python 3.3.0.
This is a preview release, and its use is not recommended in production settings.
Python 3.3 includes a range of improvements of the 3.x series, as well as easier porting between 2.x and 3.x. Major new features in the 3.3 release series are:
* PEP 380, Syntax for Delegating to a Subgenerator ("yield from") * PEP 393, Flexible String Representation (doing away with the distinction between "wide" and "narrow" Unicode builds) * PEP 409, Suppressing Exception Context * PEP 3151, Reworking the OS and IO exception hierarchy * The new "packaging" module, building upon the "distribute" and "distutils2" projects and deprecating "distutils" * The new "lzma" module with LZMA/XZ support * PEP 3155, Qualified name for classes and functions * PEP 414, explicit Unicode literals to help with porting * The new "faulthandler" module that helps diagnosing crashes * Wrappers for many more POSIX functions in the "os" and "signal" modules, as well as other useful functions such as "sendfile()"
For a more extensive list of changes in 3.3.0, see
The 3.3 whatsnews page doesn't seem to mention PEP 414 or Unicode literals at all. --Ned.
To download Python 3.3.0 visit:
http://www.python.org/download/releases/3.3.0/
Please consider trying Python 3.3.0a1 with your code and reporting any bugs you may notice to:
Enjoy!
-- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and 3.3's contributors) _______________________________________________ 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/ned%40nedbatchelder.com
On 05.03.2012 14:27, Ned Batchelder wrote:
For a more extensive list of changes in 3.3.0, see
The 3.3 whatsnews page doesn't seem to mention PEP 414 or Unicode literals at all.
Indeed. Thanks to Nick, this is now fixed. Georg
In http://mail.python.org/pipermail/python-dev/2012-March/117348.html Georg Brandl <georg@python.org> posted:
Python 3.3 includes a range of improvements of the 3.x series, as well as easier porting between 2.x and 3.x. Major new features in the 3.3 release series are:
As much as it is nice to just celebrate improvements, I think readers (particularly on the download page http://www.python.org/download/releases/3.3.0/ ) would be better served if there were an additional point about porting and the hash changes. http://docs.python.org/dev/whatsnew/3.3.html#porting-to-python-3-3 also failed to mention this, and even the changelog didn't seem to warn people about failing tests or tell them how to work around it. Perhaps something like: Hash Randomization (issue 13703) is now on by default. Unfortunately, this does break some tests; it can be temporarily turned off by setting the environment variable PYTHONHASHSEED to "0" before launching python. -jJ -- If there are still threading problems with my replies, please email me with details, so that I can try to resolve them. -jJ
Il 06 marzo 2012 20:43, Jim J. Jewett <jimjjewett@gmail.com> ha scritto:
In http://mail.python.org/pipermail/python-dev/2012-March/117348.html Georg Brandl <georg@python.org> posted:
Python 3.3 includes a range of improvements of the 3.x series, as well as easier porting between 2.x and 3.x. Major new features in the 3.3 release series are:
As much as it is nice to just celebrate improvements, I think readers (particularly on the download page http://www.python.org/download/releases/3.3.0/ ) would be better served if there were an additional point about porting and the hash changes.
http://docs.python.org/dev/whatsnew/3.3.html#porting-to-python-3-3 also failed to mention this, and even the changelog didn't seem to warn people about failing tests or tell them how to work around it.
Perhaps something like:
Hash Randomization (issue 13703) is now on by default. Unfortunately, this does break some tests; it can be temporarily turned off by setting the environment variable PYTHONHASHSEED to "0" before launching python.
-jJ
--
If there are still threading problems with my replies, please email me with details, so that I can try to resolve them. -jJ
That's why I once proposed to include whatsnew.rst changes every time a new feature is added/committed. Assigning that effort to the release manager or whoever is supposed to take care of this, is both impractical and prone to forgetfulness. --- Giampaolo http://code.google.com/p/pyftpdlib/ http://code.google.com/p/psutil/ http://code.google.com/p/pysendfile/
Le 06/03/2012 15:31, Giampaolo Rodolà a écrit :
That's why I once proposed to include whatsnew.rst changes every time a new feature is added/committed. Assigning that effort to the release manager or whoever is supposed to take care of this, is both impractical and prone to forgetfulness.
Well, it’s the call of the whatsnew author. I think amk wrote the original instructions at the top of each whatsnew file which explain that NEWS is the primary location for logging changes and whatsnew is composed from that file. If Raymond or the new whatsnew author wants to change the rules so that important changes are noted in whatsnew in addition to NEWS, nothing prevents that. Cheers
Jim J. Jewett, 06.03.2012 20:43:
Hash Randomization (issue 13703) is now on by default. Unfortunately, this does break some tests; it can be temporarily turned off by setting the environment variable PYTHONHASHSEED to "0" before launching python.
I don't think that makes it clear enough that that's just a work-around and that it's the tests that need fixing in the first place. Stefan
On 07.03.2012 08:08, Stefan Behnel wrote:
Jim J. Jewett, 06.03.2012 20:43:
Hash Randomization (issue 13703) is now on by default. Unfortunately, this does break some tests; it can be temporarily turned off by setting the environment variable PYTHONHASHSEED to "0" before launching python.
I don't think that makes it clear enough that that's just a work-around and that it's the tests that need fixing in the first place.
It's much too much for the release announcement anyway. I'll add one bullet point in the future announcements. I've added a note to what's new so that someone will add an appropriate paragraph. Georg
participants (8)
-
Georg Brandl -
Georg Brandl -
Giampaolo Rodolà -
Jim J. Jewett -
Mark Shannon -
Ned Batchelder -
Stefan Behnel -
Éric Araujo