Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8636
| From | Dmitry Shachnev <mitya57@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: pybuild renaming extensions breaks upstream code |
| Date | 2016-07-04 17:30 +0200 |
| Message-ID | <rRdYR-7jy-7@gated-at.bofh.it> (permalink) |
| References | <rQCFX-1o7-1@gated-at.bofh.it> <rQJ4J-5jF-1@gated-at.bofh.it> <rQMlX-773-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Hi Afif,
On Sun, Jul 03, 2016 at 02:37:41AM -0700, Afif Elghraoui wrote:
> It's a Python extension as far as I know. After investigating this a bit
> more, it seems that numpy's ctypeslib.load_library function can guess
> the library's extension. So for the unit test (before dh-python has
> renamed anything and the library is still librarybasename.so), it can
> guess properly if it's called as
>
> numpy.ctypeslib.load_library("librarybasename","/path/to/library/")
>
> but this won't work afterwards.
If it *is* a Python extension, you can simply import it and get the path
using the __path__ attribute.
--
Dmitry Shachnev
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread
pybuild renaming extensions breaks upstream code Afif Elghraoui <afif@debian.org> - 2016-07-03 01:40 +0200
Re: pybuild renaming extensions breaks upstream code Dmitry Shachnev <mitya57@debian.org> - 2016-07-03 08:30 +0200
Re: pybuild renaming extensions breaks upstream code Afif Elghraoui <afif@ghraoui.name> - 2016-07-03 12:00 +0200
Re: pybuild renaming extensions breaks upstream code Dmitry Shachnev <mitya57@debian.org> - 2016-07-04 17:30 +0200
csiph-web