Dear python-devel, I'm playing with packaging of my little project[1] and I'm a bit puzzled about the following issue. When I go into git repo of my project and run unittests directly: ~~~ cd ~/projects/pylatest python2 setup.py test python3 setup.py test ~~~ Or via tox (which is configured to run both python2.7 and python3.4), it all works fine and both python2 and python3 test runs reports success. I have the following section in my specfile[3], which executes the tests during the build (this is suggested by Packaging:Python guidelines): ~~~ %check %{__python2} setup.py test %{__python3} setup.py test ~~~ But when the tests are executed via rpmbuild, python2 test run reports a pass, while python3 run fails[2]. This happens both on my local machine and in copr. At this point it's clear that I'm doing something wrong and would need to inspect and fix this failure in pylatest, but I'm concerned about something else in this email: 1) How come that running tests directly gives different outcome compared to test run executed during rpm build? Note that this seems not to be caused by different python version as it also happens on my local machine (so python version is the same). 2) Is this an expected behaviour? What do I miss then? If not, is this interesting enough to check this issue deeper? [1] https://github.com/marbu/pylatest [2] https://copr-be.cloud.fedoraproject.org/results/marbu/pylatest-fedora/fed... [3] https://github.com/marbu/specfiles/blob/1911be24ff130bf7d614694de5ae340b8... -- Martin Bukatovic