Partition's set_name() not properly exported

Bug #1661297 reported by Łukasz Zemczak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyparted (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

In the python libparted bindings the Partition object exports get_name() through a name property but doesn't actually export the set_name() method along with it. This means that currently setting the name of a partition requires calling the internal PedPartition method like this:

partition._Partition__partition.set_name(name)

...which is rather ugly.

Revision history for this message
Łukasz Zemczak (sil2100) wrote :
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Upstream has prepared a fix for this, it should be part of the next pyparted release.

Revision history for this message
Olivier Gayot (ogayot) wrote :

This bug was fixed in disco and subsequent releases:

pyparted (3.11.2-2ubuntu1) disco; urgency=low

  * Merge from Debian unstable. Remaining changes:
    - debian/rules: Re-enable tests
    - debian/patches/fix-unit-tests.patch: Add patch for fixing some of the
      flag tests as _ped now returns a different exceptions for those.
    - Remove the python*-all-dbg build-deps as they do not seem to be needed
      and otherwise cause strange fatal Python errors when running the test
      suite during build.
    - Add parted to the build-dependencies, required for unit testing.
  * Dropped changes, included in Debian:
    - Add python-six to the build-dependencies, required for unit testing.

Changed in pyparted (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.