Features/Python 3.2

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Contingency Plan)
Line 40: Line 40:
 
== 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?-->
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)
 
  
 
== How To Test ==
 
== How To Test ==
Line 60: Line 55:
 
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 ==

Revision as of 18:44, 24 January 2011


Contents

Python 3.2

Summary

Update the Python 3 stack in Fedora from 3.1 to 3.2

Owner

  • Email: <dmalcolm@redhat.com>

Current status

  • Targeted release: Fedora 21
  • Last updated: 2011-01-19
  • Percentage of completion: 80%

Fedora 14 schedule currently has feature freeze on 2010-07-27

Upstream has released 3.2rc1, and it is in Fedora. The upstream release schedule currently has final release on 2011-02-12

TODO:


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

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

Contingency Plan

The bulk of the work is done, and appears stable.

Documentation

What's New In Python 3.2

Release Notes

Comments and Discussion