On Fri, Jul 22, 2005 at 04:32:08PM -0300, Ulisses Furquim wrote: > On 7/22/05, Matt Wilson <msw@xxxxxxxxx> wrote: > > What's wrong with the existing pyparted bindings? > > I tried to use it, but it's confuse and obscure, IMHO. I'm trying to > make a clean API, so anyone can use it without having to decipher it > first. Besides, there are some functions that doesn't need to be a 1x1 > translation of the libparted equivalent, so you can use it in a more > python way of coding. :-) Generally: 1) initpylibparted() should raise an exception if initialization cannot be performed (due to /proc/ not being mounted or otherwise). Currently you'll just get an error printed and types that are not safe to use. 2) there are very linux-specific things in plp_probeAllDevices(). This might not be good if you want this to be used on other platforms. In parted we tried to keep the OS-specific stuff isolated. The libparted API was fairly well documented. It should be easy to use the API documentation and get started with pyparted quickly. It seems that a lot of pylibparted and pyparted are much the same, but pylibparted just adds methods to access data whereas pyparted uses attributes. For what it's worth: this is the third python binding for parted, I believe. -- Matt Wilson rpath, Inc. msw@xxxxxxxxx
