Python 3.3
Summary
Update the Python 3 stack in Fedora from 3.2 to 3.3
Owner
- Name: Dave Malcolm
- Email: <dmalcolm@redhat.com>
Current status
- Targeted release: Fedora 18
- Last updated: 2012-04-16
- Percentage of completion: 0%
| Month | Python 3.3 release schedule) | Fedora 18 Schedule | Fedora 19 Schedule |
|---|---|---|---|
| March | 3.3.0 alpha 1: March 3, 2012 | ||
| 3.3.0 alpha 2: March 31, 2012 | |||
| April | 3.3.0 alpha 3: April 28, 2012 | ||
| May | 3.3.0 alpha 4: May 26, 2012 | Start Feature Submission Wed 2012-05-02 | |
| June | 3.3.0 beta 1: June 23, 2012: (No new features beyond this point.) | ||
| July | 3.3.0 beta 2: July 14, 2012 | ||
| Feature Submission Deadline Tue 2012-07-17 | |||
| 3.3.0 candidate 1: July 28, 2012 | |||
| Feature Freeze (Testable/Complete) Tue 2012-07-31 | |||
| Branch Fedora 18 from Rawhide Tue 2012-07-31 | |||
| August | 2012-08-07 Alpha Change Deadline | ||
| 3.3.0 candidate 2: August 11, 2012 | |||
| 2012-08-16 Alpha Release | |||
| 3.3.0 final: August 18, 2012 | |||
| September | 2012-09-11 Beta Change Deadline / Features 100% Complete |
Note: Fedora 18 schedule not yet available, so I've based the above on the (original) Fedora 16 schedule, offsetting by a year
Detailed Description
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
Compare with the Python 3.2 feature page.
We need to wait for Python 3.3 to reach feature freeze, so that the bytecode format for .pyc files is frozen, together with the ABI for extension modules.
At that point we can rebase python3 to the latest release candidate of that code. We would then need to rebuild all python 3 packages. See https://fedoraproject.org/wiki/Python3#Python_3_already_in_Fedora
For bonus points, we ought to tell "file" and "rpmlint" about the new bytecode format for .pyc files.
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.3 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.3 interpreter
Dependencies
See notes in "Scope" above.