I thought you might say that :-).&nbsp; No, I&#39;m good with this resolution.&nbsp; If I provide a patch, it will be for the LD_LIBRARY_PATH problem.<br><br>Though -- I think there&#39;s an interesting question about what the purpose of &quot;find_library()&quot; actually is, as opposed to what it&#39;s current implementation is.&nbsp; I disagree with Ronald&#39;s strict reading of the documentation.&nbsp; I think it should emulate the behavior of the dynamic linker, not the C compiler.&nbsp; That is, it should look for the libraries as &quot;ld.so&quot; (or its platform equivalent) would, because the purpose of finding them is to load them with CDLL.&nbsp; This behavior is different from what the compiler does.<br>
<br>I also think find_library() should just be moved into the ctypes library, not dangling off by itself in the otherwise unused util sub-module.<br><br>Bill<br><br><div class="gmail_quote">On Wed, May 21, 2008 at 11:39 AM, Thomas Heller &lt;<a href="mailto:report@bugs.python.org">report@bugs.python.org</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:theller@ctypes.org">theller@ctypes.org</a>&gt; added the comment:<br>
<br>
</div>Thanks, Ronald. &nbsp;Sounds like this bug could be closed then.<br>
<br>
Bill, if you want a library search function with different semantics,<br>
I suggest you open a feature request, describe the sematics that<br>
should be used and (ideally) provide a patch.<br>
<div><div></div><div class="Wj3C7c"><br>
__________________________________<br>
Tracker &lt;<a href="mailto:report@bugs.python.org">report@bugs.python.org</a>&gt;<br>
&lt;<a href="http://bugs.python.org/issue2783" target="_blank">http://bugs.python.org/issue2783</a>&gt;<br>
__________________________________<br>
</div></div></blockquote></div><br>