Re: Compiled C modules are not found by test suite (Was: Help needed for python-biopython which splits up modules into two packages per Python version)

Hello, I got the code and the debian directory. I confirmed that extension modules are in the build directory, not alongside the Python modules, so they can’t be imported from tests. There are two ways to fix that: either make distutils build the extensions alongside the Python module

Re: pybuild: where to put --test-pytest?

>>> ROOT/python-dugong-2.1/.pybuild/pythonX.Y_3.4/build. The latter seems to [...] > I was assuming that there's some rationale for pybuild looking for the > tests in this directory. If they have to be copied there manually, or if > pybuild has to be told to look for them elsewhere, then why look f

Re: pybuild: where to put --test-pytest?

Piotr Ożarowski writes: > [Nikolaus Rath, 2014-03-14] >> It seems that pybuild tries to find the tests in some temporary >> directory: >> >> $ debuild -us -uc >> [] >> make[1]: Leaving directory `ROOT/python-dugong-2.1' >>dh_auto_test -O--buildsystem=pybuild >> I: pybuild base:170: cd ROO

Re: Compiled C modules are not found by test suite (Was: Help needed for python-biopython which splits up modules into two packages per Python version)

On Wed, Mar 12, 2014 at 01:20:38AM -0400, Éric Araujo wrote: > Le 05/03/2014 10:31, Andreas Tille a écrit : > >I have noted another problem: I worked a bit > >on the tests and noticed that those tests that are including compiled C > >code are failing. Is there anything in addition I need to do to

Re: pybuild: where to put --test-pytest?

[Nikolaus Rath, 2014-03-14] > It seems that pybuild tries to find the tests in some temporary > directory: > > $ debuild -us -uc > [] > make[1]: Leaving directory `ROOT/python-dugong-2.1' >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:170: cd ROOT/python-dugong-2.1/.pybuild/python