[Julien Cristau, 2015-10-06]
> As far as I can tell, this is caused by a change in pybuild: instead of
> running something like "python setup.py test" from the toplevel source
> directory (which works), it runs "python2.7 -m nose" from
> .pybuild/pythonX.Y_2.7/build. The latter directory is missing
> blockdiag.egg-info, which means pkg_resources doesn't find any entry
> points. I'm tempted to reassign this to dh-python.
I will definitely not go back to running tests from package root
directory (due to . in sys.path or 2to3 issues).
I might consider copying egg-info dir to the build dir, though.
What I suggest to do right now is adding this line to debian/rules:
export PYBUILD_BEFORE_TEST=cp -r foo.egg-info {build_dir}
and about `setup.py test` vs. `pythonX.Y -m nose` - I'd love to have a
standard API for running tests, but that's something you need to talk
with Python upstream
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
