SONAME for python modules is bad? (aka multiple module version)

[mathieu]

As far as I know there has not been any consensus on how to install
multiple version of a same module in python ? What are the recommended
mechanism ?

I could not find any documentation on the subject. Does anyone sees
any issue with using standard SONAME mechanism when installing a
python module ?

Thanks,

ref:
http://mail.python.org/pipermail/pythonmac-sig/2009-January/020936.html

 

[Diez B. Roggisch]

As far as I know there has not been any consensus on how to install
multiple version of a same module in python ? What are the recommended
mechanism ?

I use virtualenvs for everything. Especially on unixish OSes this
usually works without problems. On windows, things are a bit different,
as sometimes you only get binary installers that insist on installing
into the base-installation.

I could not find any documentation on the subject. Does anyone sees
any issue with using standard SONAME mechanism when installing a
python module ?

I don't understand that. You mean the .so.X.Y.Z-thingy under *ix? That
would essentially be the pkg_resources.require-road, yes. But as it's
not widely adopted, it will cause you troubles because some packages
won't declare their dependencies properly.

Diez