well, yeah -- but I would advise to run tests against "installed" version of the software -- who knows what was missing from their MANIFEST.in or setup.py files... although might require few more custom lines, testing against installed version IMHO provides better QA. Moreover some modules/projects even forbid (or discourage) in-source testing (e.g. IIRC numpy)
also, depending on the setup, it might be wasting CPU while building extensions multiple times -- first in-place, then for installation Just my 0.1 cents On Tue, 18 Oct 2011, Ole Streicher wrote: > python setup.py build_ext -i > which builds the extension in-place. So my debian/rules looks like > override_dh_auto_test: > python setup.py build_ext -i && nosetests tests/test.py > This works fine for me, and I hope it will survive the review :-) -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111018144710.gg10...@onerussian.com
