m (Anaconda/Features/NewPyParted moved to Features/NewPyParted) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 12: | Line 12: | ||
== Current status == | == Current status == | ||
* Targeted release: Fedora 11 | * Targeted release: Fedora 11 | ||
* Last updated: 2009-02- | * Last updated: 2009-02-27 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
* Note that although this work is done for F11, FESCO f=didnt think this was big enough to be a feature, which is why its lingering in featureincomplete | |||
== Detailed Description == | == Detailed Description == | ||
Upstream (David) | Upstream (David) has a new pyparted to be included as part of the standard parted. We have switched anaconda to using this in February. | ||
Chris Lumens and David Cantrell started a rewrite of pyparted to completely expose the libparted C API to Python programmers. It became difficult working with pyparted in anaconda because certain pieces of information were not available and the module would have to be slightly expanded. | Chris Lumens and David Cantrell started a rewrite of pyparted to completely expose the libparted C API to Python programmers. It became difficult working with pyparted in anaconda because certain pieces of information were not available and the module would have to be slightly expanded. | ||
The rewrite will come in two phases. The first phase will be reimplementation of the current pyparted API on top of the new _ped module. This ensures an easy transition within anaconda. The second phase will complete the rewrite of the new parted module's classes. Eventually the deprecated API code can be removed. | The rewrite will come in two phases. The first phase will be reimplementation of the current pyparted API on top of the new _ped module. This ensures an easy transition within anaconda. The second phase will complete the rewrite of the new parted module's classes. Eventually the deprecated API code can be removed. | ||
Both phases are complete, would like to add additional unit tests as time permits. | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 29: | Line 32: | ||
== Scope == | == Scope == | ||
Internal to anaconda's partitioning code. | Internal to anaconda's partitioning code. Potentially useful to other projects. | ||
== Test Plan == | == Test Plan == | ||
| Line 57: | Line 60: | ||
---- | ---- | ||
[[Category: | [[Category:FeaturePageIncomplete]] | ||
Latest revision as of 17:43, 17 April 2009
Switch Anaconda to Use New PyParted
Summary
A new pyparted is being worked on as part of the upstream parted project. Anaconda will switch to using this for the Storage rewrite project.
Owner
- Name: DavidCantrell
Current status
- Targeted release: Fedora 11
- Last updated: 2009-02-27
- Percentage of completion: 100%
- Note that although this work is done for F11, FESCO f=didnt think this was big enough to be a feature, which is why its lingering in featureincomplete
Detailed Description
Upstream (David) has a new pyparted to be included as part of the standard parted. We have switched anaconda to using this in February.
Chris Lumens and David Cantrell started a rewrite of pyparted to completely expose the libparted C API to Python programmers. It became difficult working with pyparted in anaconda because certain pieces of information were not available and the module would have to be slightly expanded.
The rewrite will come in two phases. The first phase will be reimplementation of the current pyparted API on top of the new _ped module. This ensures an easy transition within anaconda. The second phase will complete the rewrite of the new parted module's classes. Eventually the deprecated API code can be removed.
Both phases are complete, would like to add additional unit tests as time permits.
Benefit to Fedora
Closer to upstream, picks up extensive unit tests that have been added, more maintainable.
Scope
Internal to anaconda's partitioning code. Potentially useful to other projects.
Test Plan
Test that installs can correctly partition in all the currently supported ways. New code also includes extensive unit tests.
User Experience
No change.
Dependencies
Getting the pyparted bits working well enough to do the switch
Contingency Plan
Keep using the old pyparted
Documentation
No impact; not visible to users.
Release Notes
No impact; not visible to users so no release note needed.