Upstream has released 3.2rc1, and it is in Fedora. The upstream [http://www.python.org/dev/peps/pep-0392/ release schedule] currently has final release on 2011-02-12

+

Upstream has now released 3.2 (see the upstream [http://www.python.org/dev/peps/pep-0392/ release schedule])

−

TODO:

+

Latest in F15 is 3.2 (via [https://admin.fedoraproject.org/updates/python3-3.2-1.fc15 an errata])

−

* verify status of bytecode. Last change seems to have been in [http://svn.python.org/view?view=rev&revision=84501 upstream revision 84501], which [http://svn.python.org/view/python/branches/py3k/Python/import.c?r1=84501&r2=84500&pathrev=84501 changed the magic number of .pyc/.pyo files to 3170]

+

+

Latest in F16 is 3.2

+

+

The final change to the bytecode format for 3.2 was in [http://svn.python.org/view?revision=84686&view=revision upstream revision 84686], which [http://hg.python.org/cpython/rev/252895d49157 changed the magic number of .pyc/.pyo files to 3180]. The latest version of rpmlint for F15 (and rawhide) correctly checks for this bytecode version in python 3 rpms (see {{bz|672352}})

+

+

The "file" command has been taught about 3.2's .pyc/.pyo files: {{bz|678458}} (though so far only fixed in F16 onwards)

<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->

<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->

−

Python 3.2 is the latest release of the Python 3 language. Although the [http://www.python.org/dev/peps/pep-3003/ core language has been frozen] (to allow the [http://fedoraproject.org/wiki/SIGs/Python#Python_Runtimes non-CPython implementation of Python] to "catch up" with CPython), 3.2 contains [http://docs.python.org/dev/whatsnew/3.2.html hundreds of fixes and tweaks throughout].

+

Python 3.2 is the latest release of the Python 3 language. Although the [http://www.python.org/dev/peps/pep-3003/ core language has been frozen] (to allow the [http://fedoraproject.org/wiki/SIGs/Python#Python_Runtimes non-CPython implementation of Python] to "catch up" with CPython), 3.2 contains [http://docs.python.org/dev/whatsnew/3.2.html hundreds of fixes and tweaks throughout], a few of which I'm responsible for ;-)

== Benefit to Fedora ==

== Benefit to Fedora ==

Line 44:

Line 48:

There have been some slight changes to the on-disk layout of how Python organizes extension modules: [http://www.python.org/dev/peps/pep-3147/ PEP-3147] and [http://www.python.org/dev/peps/pep-3149/ PEP-3149].

There have been some slight changes to the on-disk layout of how Python organizes extension modules: [http://www.python.org/dev/peps/pep-3147/ PEP-3147] and [http://www.python.org/dev/peps/pep-3149/ PEP-3149].

−

https://fedoraproject.org/wiki/Python3#Python_3_already_in_Fedora indicates that as of Fedora 15 there are currently about 25-30 extension modules for Python 3 available via RPM. These will need rebuilding to cope with disk layout changes, and for the latest .pyc/.pyo bytecode format. I will do these as necessary before the release. Many have already been done by package maintainers.

+

https://fedoraproject.org/wiki/Python3#Python_3_already_in_Fedora indicates that as of Fedora 15 there are currently about 25-30 extension modules for Python 3 available via RPM. These will need rebuilding to cope with disk layout changes, and for the latest .pyc/.pyo bytecode format. I believe that [https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild the Fedora 15 mass rebuild] will cover this; I will do any remaining rebuilds as necessary before the release. Many have already been done by package maintainers.

== How To Test ==

== How To Test ==

Line 72:

Line 76:

== Dependencies ==

== Dependencies ==

<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? -->

<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? -->

+

See notes in "Scope" above.

== Contingency Plan ==

== Contingency Plan ==

Line 87:

Line 92:

== Comments and Discussion ==

== Comments and Discussion ==

−

* See [[Talk:Features/YourFeatureName]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->

+

* See [[Talk:Features/Python_3.2]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->

−

[[Category:FeaturePageIncomplete]]

+

[[Category:FeatureAcceptedF15]]

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->

<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->

Benefit to Fedora

Fedora aims to showcase the latest in free and open source software - we should have the most recent release of Python 3.

Scope

The core python3 src.rpm has been rebuilt with the latest 3.2 code.

There have been some slight changes to the on-disk layout of how Python organizes extension modules: PEP-3147 and PEP-3149.

https://fedoraproject.org/wiki/Python3#Python_3_already_in_Fedora indicates that as of Fedora 15 there are currently about 25-30 extension modules for Python 3 available via RPM. These will need rebuilding to cope with disk layout changes, and for the latest .pyc/.pyo bytecode format. I believe that the Fedora 15 mass rebuild will cover this; I will do any remaining rebuilds as necessary before the release. Many have already been done by package maintainers.

How To Test

Interested testers do not need special hardware. If you have a favorite Python 3 script, module, or application, please test it with Python 3.2 and verify that it still works as you expect.

My own test plan:

Smoketest of the interpreter

Run the upstream regression test suite (this is done during %check)

User Experience

Users should not notice any difference, other than the availability of the 3.2 interpreter

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, and JBoss are trademarks or registered trademarks of
Red Hat, Inc. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community
maintained site. Red Hat is not responsible for content.