On 06/24/2012 12:47 PM, Thomas Jarosch wrote:
> The python wrapper is more complex: If we just rename
> the module from "ftdi" to "ftdi1", all client code would
> need adaption, too. Hopefully there's a way to avoid this. Michel?
Seems like it's not easily possible.
Basically we have two options here:
a) Rename everything to "ftdi1" for the python wrapper.
All client code needs to be changed.
This would allow parallel installation of libftdi 0.x
or future libftdi versions.
b) Stick to "ftdi" for the .so library name and the
python module name.
Client code stays unchanged. Parallel installation
of the wrapper module from libftdi 0.x / 1.x is not possible.
Distributions could rename the old wrapper from libftdi 0.x to "ftdi0"
and patch client code, if needed at all. Though it's very hard to
detect python code breakage without running the code.
Right now option b) looks better to me.
Opinions?
Thomas
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
