Re: Python3 search path order when building Debian package

[Piotr Ożarowski <piotr@debian.org>]

> override_dh_auto_test:
> ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS)))
>         @echo "===> Running tests"
>         set -e && set -x && for i in 2.7 $(PYTHON3S) ; do \
>                 PYMAJOR=`echo $$i | cut -d'.' -f1` ; \
>                 echo "===> Testing with python$$i (python$$PYMAJOR)" ; \
>                 rm -rf .testrepository ; \
>                 testr-python$$PYMAJOR init ; \
>                 TEMP_REZ=`mktemp -t` && \
>                 PYTHONPATH=$(CURDIR) PYTHON=python$$i
> testr-python$$PYMAJOR run --subunit | tee $$TEMP_REZ | subunit2pyunit ; \
>                 cat $$TEMP_REZ | subunit-filter -s --no-passthrough |
> subunit-stats ; \
>                 rm -f $$TEMP_REZ ; \
>                 testr-python$$PYMAJOR slowest ; \
>         done
> endif
> 
> If I do this, then it works for 2.7, not for 3.4.

does the module from $(CURDIR) work with 3.X and 2.X without 2to3?
where does build target put it?
does testr-python$$PYMAJOR touch sys.path?
-- 
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