[issue2936] ctypes.util.find_library() doesn't consult LD_LIBRARY_PATH

[Bill Janssen]

Bill Janssen <[EMAIL PROTECTED]> added the comment:

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 "libfoo.so.N" (or, on Darwin, "libfoo.N.dylib")?
That would be very useful.  Right now, I don't see the use case for
find_library().

Bill

On Fri, May 30, 2008 at 1:58 PM, Thomas Heller <[EMAIL PROTECTED]>
wrote:

>
> Thomas Heller <[EMAIL PROTECTED]> added the comment:
>
> > The question is, which linker?  I think it should be ld.so, 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:
> http://docs.python.org/lib/ctypes-finding-shared-libraries.html
>
> _______________________________________
> Python tracker <[EMAIL PROTECTED]>
> <http://bugs.python.org/issue2936>
> _______________________________________
>

Added file: http://bugs.python.org/file10487/unnamed

_______________________________________
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2936>
_______________________________________
Yes, I&#39;ve read that explanation, but I still don&#39;t see what the point 
of find_library() is.&nbsp; Are you trying to resolve a possibly ambiguous 
reference to a shared library to the one which is used by the Python 
interpreter?&nbsp; If that&#39;s the case (and that&#39;s what the code seems 
to do), how about calling it &quot;find_library_used_by_python&quot;, and have 
another function, perhaps called &quot;find_library&quot;, which, given a 
partial name like &quot;foo&quot;, 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 
&quot;libfoo.so.N&quot; (or, on Darwin, &quot;libfoo.N.dylib&quot;)?&nbsp; That 
would be very useful.&nbsp; Right now, I don&#39;t see the use case for 
find_library().<br>
<br>Bill<br><br><div class="gmail_quote">On Fri, May 30, 2008 at 1:58 PM, 
Thomas Heller &lt;<a href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a>&gt; 
wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid 
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
Thomas Heller &lt;<a href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a>&gt; 
added the comment:<br>
<br>
</div><div class="Ih2E3d">&gt; The question is, which linker? &nbsp;I think it 
should be ld.so, which links &quot;on<br>
&gt; demand&quot;, and does pay attention to LD_LIBRARY_PATH. &nbsp;I&#39;m not 
sure what the<br>
&gt; point of find_library() is, otherwise.<br>
<br>
</div>The best explanation is in the python docs:<br>
<a href="http://docs.python.org/lib/ctypes-finding-shared-libraries.html"; 
target="_blank">http://docs.python.org/lib/ctypes-finding-shared-libraries.html</a><br>
<div><div></div><div class="Wj3C7c"><br>
_______________________________________<br>
Python tracker &lt;<a href="mailto:[EMAIL PROTECTED]">[EMAIL 
PROTECTED]</a>&gt;<br>
&lt;<a href="http://bugs.python.org/issue2936"; 
target="_blank">http://bugs.python.org/issue2936</a>&gt;<br>
_______________________________________<br>
</div></div></blockquote></div><br>

_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com