Bill Janssen <[EMAIL PROTECTED]> added the comment:
I thought you might say that :-). No, I'm good with this resolution. If I
provide a patch, it will be for the LD_LIBRARY_PATH problem.
Though -- I think there's an interesting question about what the purpose of
"find_library()" actually is, as opposed to what it's current implementation
is. I disagree with Ronald's strict reading of the documentation. I think
it should emulate the behavior of the dynamic linker, not the C compiler.
That is, it should look for the libraries as "ld.so" (or its platform
equivalent) would, because the purpose of finding them is to load them with
CDLL. This behavior is different from what the compiler does.
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.
Bill
On Wed, May 21, 2008 at 11:39 AM, Thomas Heller <[EMAIL PROTECTED]>
wrote:
>
> Thomas Heller <[EMAIL PROTECTED]> added the comment:
>
> Thanks, Ronald. Sounds like this bug could be closed then.
>
> Bill, if you want a library search function with different semantics,
> I suggest you open a feature request, describe the sematics that
> should be used and (ideally) provide a patch.
>
> __________________________________
> Tracker <[EMAIL PROTECTED]>
> <http://bugs.python.org/issue2783>
> __________________________________
>
Added file: http://bugs.python.org/file10394/unnamed
__________________________________
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2783>
__________________________________
I thought you might say that :-). No, I'm good with this
resolution. If I provide a patch, it will be for the LD_LIBRARY_PATH
problem.<br><br>Though -- I think there's an interesting question about
what the purpose of "find_library()" actually is, as opposed to what
it's current implementation is. I disagree with Ronald's strict
reading of the documentation. I think it should emulate the behavior of
the dynamic linker, not the C compiler. That is, it should look for the
libraries as "ld.so" (or its platform equivalent) would, because the
purpose of finding them is to load them with CDLL. 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 <<a href="mailto:[EMAIL PROTECTED]">[EMAIL
PROTECTED]</a>> 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 <<a href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a>>
added the comment:<br>
<br>
</div>Thanks, Ronald. 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 <<a href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a>><br>
<<a href="http://bugs.python.org/issue2783";
target="_blank">http://bugs.python.org/issue2783</a>><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
