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 martin.panter
Recipients automatthias, jcea, martin.panter, risto3
Date 2016-04-28.06:43:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461825816.93.0.652872207551.issue19317@psf.upfronthosting.co.za>
In-reply-to
Content
I am realizing that many people like to use find_library() as a way of converting a portable name like “magic” (from building with -lmagic) into a platform-specific name (libmagic.so.1, libmagic.dylib, magic.dll, etc), and then pass this to LoadLibrary() or equivalent. So searching Python’s runpath would probably be valid for that use case.

IMO the extra searching is inefficient, and not robust if there is more than one version of the library. Personally I would be more interested in adding an alternative function, maybe make_library_name("magic", "1") -> "libmagic.so.1", or cdll.LoadLibraryByPortableName("magic", "1").
History
Date User Action Args
2016-04-28 06:43:36martin.pantersetrecipients: + martin.panter, jcea, automatthias, risto3
2016-04-28 06:43:36martin.pantersetmessageid: <1461825816.93.0.652872207551.issue19317@psf.upfronthosting.co.za>
2016-04-28 06:43:36martin.panterlinkissue19317 messages
2016-04-28 06:43:36martin.pantercreate