On Tue, Jul 26, 2005 at 10:33:45PM -0300, Ulisses Furquim wrote: > > > Changing the constructors around is pretty. I changed it around > > I'm not sure I understood what you meant.. Do you mean pylibparted > should have PedDevice.get() and PedDisk.new(), for example? I meant that we could change the constructors in pyparted around easily. > > We always implemented this in application-specific code, since many > > users of pyparted have their own hardware detection code that handles > > cases that ped_device_probe_all() misses. > > Ok, so users can always use their own hardware detection code and do > pylibparted.PedDevice(devicepath) to create a PedDevice object for > each device they found. True, but it may just be that the C binding isn't the right place to have probing code. > Ok. I'll implement those iterators in pylibparted. :-) My point is that I don't understand why a totally new project is needed. There are already _lots_ of users of pyparted. Many distros are using it just by basing installer on anaconda. There's other software that's using pyparted as well. I have yet to be convinced that we _really_ need a 4th parted python binding. -- Matt Wilson rpath, Inc. msw@xxxxxxxxx
