From Fedora Project Wiki
< Features
m (→Current status: add link to rpmlint bug) |
|||
| (36 intermediate revisions by 3 users not shown) | |||
| Line 17: | Line 17: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/15 | Fedora 15 ]] | ||
* Last updated: | * Last updated: 2011-04-07 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
[ | Upstream has now released 3.2 (see the upstream [http://www.python.org/dev/peps/pep-0392/ release schedule]) | ||
Latest in F15 is 3.2 (via [https://admin.fedoraproject.org/updates/python3-3.2-1.fc15 an errata]) | |||
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) | |||
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | <!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | ||
| Line 33: | Line 35: | ||
== Detailed Description == | == Detailed Description == | ||
<!-- 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], a few of which I'm responsible for ;-) | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?--> | ||
Fedora aims to showcase the latest in free and open source software - we should have the most recent release of Python 3. | |||
== Scope == | == Scope == | ||
<!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
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: [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 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 54: | Line 64: | ||
3. What are the expected results of those actions? | 3. What are the expected results of those actions? | ||
--> | --> | ||
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 == | == User Experience == | ||
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
Users should not notice any difference, other than the availability of the 3.2 interpreter | |||
== 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 == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
The bulk of the work is done, and appears stable. | |||
== Documentation == | == Documentation == | ||
| Line 71: | Line 89: | ||
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | ||
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | ||
The system Python 3 stack has been upgraded to 3.2 (the system Python 2 stack remains at 2.7), bringing in hundreds of fixes and tweaks; for a list of changes see http://docs.python.org/dev/whatsnew/3.2.html | |||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[Talk:Features/ | * 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: | [[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 --> | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | ||
[[Category:Python]] | |||
Revision as of 17:50, 7 April 2011
Python 3.2
Summary
Update the Python 3 stack in Fedora from 3.1 to 3.2
Owner
- Name: Dave Malcolm
- Email: <dmalcolm@redhat.com>
Current status
- Targeted release: Fedora 15
- Last updated: 2011-04-07
- Percentage of completion: 100%
Upstream has now released 3.2 (see the upstream release schedule)
Latest in F15 is 3.2 (via an errata)
Latest in F16 is 3.2
The final change to the bytecode format for 3.2 was in upstream revision 84686, which 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 RHBZ #672352)
The "file" command has been taught about 3.2's .pyc/.pyo files: RHBZ #678458 (though so far only fixed in F16 onwards)
Detailed Description
Python 3.2 is the latest release of the Python 3 language. Although the core language has been frozen (to allow the non-CPython implementation of Python to "catch up" with CPython), 3.2 contains hundreds of fixes and tweaks throughout, a few of which I'm responsible for ;-)
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
Dependencies
See notes in "Scope" above.
Contingency Plan
The bulk of the work is done, and appears stable.
Documentation
Release Notes
The system Python 3 stack has been upgraded to 3.2 (the system Python 2 stack remains at 2.7), bringing in hundreds of fixes and tweaks; for a list of changes see http://docs.python.org/dev/whatsnew/3.2.html