Re: pybuild renaming extensions breaks upstream code

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 > rename

Re: pybuild renaming extensions breaks upstream code

Hi, Dmitry, Thanks for your reply على السبت 2 تـمـوز 2016 ‫23:03، كتب Dmitry Shachnev: >> Is there a better way around this problem? > If it is not a Python extension but rather a generic plugin, you can tell > dh_python2 not to touch it (i.e. via the -X flag), or better install it to > some pri

Re: pybuild renaming extensions breaks upstream code

Hi Afif, On Sat, Jul 02, 2016 at 04:20:11PM -0700, Afif Elghraoui wrote: > Hello, > I'm maintaining a set of python modules that have this pattern of code > for finding compiled extensions (this example is from the kineticstools > package): > > [...] > > When the package is built and the architect

pybuild renaming extensions breaks upstream code

Hello, I'm maintaining a set of python modules that have this pattern of code for finding compiled extensions (this example is from the kineticstools package): ~~~ if platform.system() == "Windows": libfn = "tree_predict.dll" path = os.path.dirname(os.path.abspath(