Howdy,
I need to support both 32-bit and 64-bit versions of compiled python
modules that cannot be installed into the default search path of the
python interpreter(s). I use PYTHONPATH to point to the module
installations, but I have a problem: I don't know, a priori, whether
the user will be run
On Mar 24, 2:23 pm, "Martin v. Löwis" wrote:
> > So, for example, if I upgrade to libpython2.6.so.1.1
>
> How do you do that? There won't ever be such a library. They
> will always be called libpython2.6.so.1.0.
>
> So no, no minor revision gets encoded into the SONAME.
Then what's the significan
I'm wondering why the SONAME in libpython.so has a minor revision
encoded in it; for example (on Linux):
$ readelf -d libpython2.6.so | grep SONAME
0x000e (SONAME) Library soname:
[libpython2.6.so.1.0]
Because of this, if I compile an app against this library (with '-L/
u
