Nikolaus Rath added the comment:
Matt, I believe in that case it's still a documentation issue, because then the
documentation probably should say that using absolute paths to libraries is a
bad idea in general.
--
___
Python tracker
Matt Jones added the comment:
Is this really a documentation issue? Is it not generally understood that
using absolute paths to libraries is a bad idea due to the amount of
PATH/symlink spaghetti that the average file system contains?
--
nosy: +Matt.Jones
Mark Lawrence added the comment:
Would someone like to propose a documentation patch that clarifies this
situation.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7760
Marcin Bachry hegel...@gmail.com added the comment:
In the libc case you shouldn't give absolute path in CDLL: CDLL('libc.so.6') is
better. You use /lib/libc.so.6 path, but Python (and ctypes.so) actually uses
something like /lib/tls/i686/cmov/libc.so.6 - these are two separate
libraries with
Nikolaus Rath nikol...@rath.org added the comment:
I can confirm that without the path it works for me too.
But I have to admit that I don't really understand your explanation. Should I
generally not use full paths with CDLL? Or just in the case of libc?
In either case, I think the ctypes
New submission from Nikolaus Rath nikol...@rath.org:
On my system (Ubuntu Karmic, Python 2.6.4 (r264:75706, Dec 7 2009, 18:45:15),
Kernel 2.6.31-17-generic, libc6 2.10.1-0ubuntu16) the attached test script
produces the following output:
Traceback (most recent call last):
File test1.py,
Changes by Brian Curtin cur...@acm.org:
--
priority: - normal
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7760
___
___
