On 06/06/10 11:21, PICCA Frédéric-Emmanuel wrote: >> Since the Debian Policy forbids packages that don't provide the same >> functionality (like these two modules) to conflict with each other, you >> cannot >> go that route. You could probably hack it with .pth so that you don't need a >> package Conflict, but that's just a hack and the problem is still there, so >> in >> the end one will need to be renamed. > > what .pth hack are you talking about ?
You put the module in some dir and then use a .pth so you can import it normally. This will avoid the file conflict, but not the namespace one, and I'm not sure what would happen if you install both modules, so you better prod upstream into renaming it. Cheers, Emilio -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c0b6ed8.8000...@debian.org
