RE : python module name conflict

[PICCA Frédéric-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr>]

> Hi Frédéric,

Hello

> IMHO one of them needs to be renamed, probably the newest one. If the one you
> want to package is only used in the project upstream mentions, renaming that one
> would be a good option They can temporarily do something like this:

> try:
>    import newname
> except ImportError:
>    try:
>        import tau as newname
>    except:
>        print 'newname not available'
>        sys.exit(1)

>And use 'newname' in all the code, until some time has passed.

ok so with this trick, they can do a smooth transition.
then at the end of the transition, I should package it with the right name.

> 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 ?

Cheers,
Frederic