This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author janssen
Recipients janssen, jcea, schmir, theller
Date 2008-05-31.18:31:47
SpamBayes Score 0.0002427008
Marked as misclassified No
Message-id <>
In-reply-to <>
Yes, I've read that explanation, but I still don't see what the point of
find_library() is.  Are you trying to resolve a possibly ambiguous reference
to a shared library to the one which is used by the Python interpreter?  If
that's the case (and that's what the code seems to do), how about calling it
"find_library_used_by_python", and have another function, perhaps called
"find_library", which, given a partial name like "foo", searches the
LD_LIBRARY_PATH (or, on Darwin, the DYLD_LIBRARY_PATH), if set, then the
standard system locations, the, on Darwin, the DYLD_FALLBACK_LIBRARY_PATH,
to find a library called "" (or, on Darwin, "libfoo.N.dylib")?
That would be very useful.  Right now, I don't see the use case for


On Fri, May 30, 2008 at 1:58 PM, Thomas Heller <>

> Thomas Heller <> added the comment:
> > The question is, which linker?  I think it should be, which links
> "on
> > demand", and does pay attention to LD_LIBRARY_PATH.  I'm not sure what
> the
> > point of find_library() is, otherwise.
> The best explanation is in the python docs:
> _______________________________________
> Python tracker <>
> <>
> _______________________________________
File name Uploaded
unnamed janssen, 2008-05-31.18:31:44
Date User Action Args
2008-05-31 18:31:56janssensetspambayes_score: 0.000242701 -> 0.0002427008
recipients: + janssen, theller, jcea, schmir
2008-05-31 18:31:47janssenlinkissue2936 messages
2008-05-31 18:31:47janssencreate