Features/Python3ForCriticalComponents
From FedoraProject
< Features(Difference between revisions)
m (→Detailed Description) |
(Short list of packages that need to be updated based on anaconda.spec.in from newui branch) |
||
| (3 intermediate revisions by one user not shown) | |||
| Line 31: | Line 31: | ||
== 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. --> | ||
| − | 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. | + | Fedora's installer, [[Anaconda]], and update tools ([[Tools/yum|yum]]) are implemented in [[SIGs/Python|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) | 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) | ||
| Line 39: | Line 39: | ||
TODO: who is to do this work? | TODO: who is to do this work? | ||
| − | TODO: | + | TODO: do each of the upstreams want to do this? anaconda? yum? how will each one do it? |
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 46: | Line 46: | ||
== 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?--> | ||
| + | * Anaconda | ||
| + | * pyparted | ||
| + | * yum | ||
| + | * pykickstart | ||
| + | * pygobject3 | ||
| + | * python-pyblock | ||
| + | * python-urlgrabber | ||
| + | * python-nose | ||
| + | * rpm-python | ||
| + | * python-meh | ||
| + | * python-babel | ||
| + | * libuser-python | ||
| + | * newt-python | ||
| + | * python-cryptsetup | ||
| + | * dbus-python | ||
| + | * cracklib-python | ||
| + | * python-bugzilla | ||
| + | * python-nss | ||
| + | * pytz | ||
| + | * libselinux-python | ||
== How To Test == | == How To Test == | ||
| Line 89: | Line 109: | ||
<!-- 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]] | ||
Latest revision as of 21:05, 14 April 2012
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.
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.
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
Make sure you click watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed
Contents |
[edit] Python 3 for Critical Components
[edit] 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).
[edit] Owner
- Name: Dave Malcolm
- Email: <dmalcolm@redhat.com>
[edit] Current status
- Targeted release: [[Releases/<number> | Fedora <number> ]]
- Last updated: 2010-11-17
- Percentage of completion: 0%
[edit] 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?
[edit] Benefit to Fedora
[edit] Scope
- Anaconda
- pyparted
- yum
- pykickstart
- pygobject3
- python-pyblock
- python-urlgrabber
- python-nose
- rpm-python
- python-meh
- python-babel
- libuser-python
- newt-python
- python-cryptsetup
- dbus-python
- cracklib-python
- python-bugzilla
- python-nss
- pytz
- libselinux-python
