Hi Éric,
On Fri, Mar 14, 2014 at 07:15:26PM -0400, Éric Araujo wrote:
There are two ways to fix that: either make distutils build the
extensions alongside the Python modules, or make the test import all
code from the build directory. I’m surprised that this isn’t a
common issue for PMPT.
Hi,
I tried the first solution and did not see a difference in tests:
both times, 223 tests were run successfully. I’d like to reproduce
the errors you mention to be sure that any change I make is actually
a fix.
I guess this is the solution since if the C modules are not found the
test
On 15.03.2014 00:15, Éric Araujo wrote:
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
[CC me please]
Hi,
I am trying to work on :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740907
Basically I have an example package (dh_installexamples) which needs
to depends on python-flask. Depending whether my users installed
python3-openslide or python-openslide, I need to
[Éric Araujo, 2014-03-15]
Hi,
I tried the first solution and did not see a difference in tests:
both times, 223 tests were run successfully. I’d like to reproduce
the errors you mention to be sure that any change I make is actually
a fix.
I guess this is the solution since if the C
On 03/15/2014 07:39 PM, Mathieu Malaterre wrote:
[CC me please]
Hi,
I am trying to work on :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740907
Basically I have an example package (dh_installexamples) which needs
to depends on python-flask. Depending whether my users
On Mar 15, 2014, at 12:06 AM, Piotr Ożarowski wrote:
In distutils build plugin, pybuild already checks for test_suite in
setup.py (which apparently is not the only case where
`{interpreter} setup.py test` should be invoked), invokes
`{interpreter} -m unittest discover -v`... but only for some
7 matches
Mail list logo