Features/Python3ForCriticalComponents

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
m (Detailed Description)
(Detailed Description)
Line 39: Line 39:
 
TODO: who is to do this work?
 
TODO: who is to do this work?
  
TODO: how does each upstream want to do this?  anaconda?  yum?
+
TODO: do each of the upstreams want to do this?  anaconda?  yum?  how will each one do it?
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==

Revision as of 19:19, 17 November 2010

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.
Important.png
Set a Page Watch
Make sure you click watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler
Note.png
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed



Contents

Python 3 for Critical Components

Summary

The Python components at the very heart of Fedora have been migrated from Python 2 to Python 3. This includes the system installer (anaconda) and the updater (yum).


Owner

  • Email: <dmalcolm@redhat.com>

Current status

  • Targeted release: [[Releases/<number> | Fedora <number> ]]
  • Last updated: 2010-11-17
  • Percentage of completion: 0%


Detailed Description

Fedora's installer, Anaconda, and update tools yum are implemented in Python. Migrating them from Python 2 to Python 3 requires them both to be migrated together, along with any modules they use. It also requires all yum plugins to be migrated.

This is a big task, and may take several Fedora releases to accomplish, laying the groundwork in, say, Fedora 15 by porting some of the dependencies, and eventually "flicking the switch" in a later release (say, Fedora 16)

TODO: create huge tracker bug covering the various dependencies

TODO: who is to do this work?

TODO: do each of the upstreams want to do this? anaconda? yum? how will each one do it?

Benefit to Fedora

Scope

How To Test

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion