[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Python < 3.5 tests



Probably the discover improvements in 3.5 try using python -m unittest2.discover

On 8 Oct 2015 10:12, "Brian May" <brian@microcomaustralia.com.au> wrote:
Hello,

When debugging #801208, I noticed the following output:

   dh_auto_test -O--buildsystem=pybuild
   I: pybuild base:170: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build;
   python2.7 -m unittest discover -v

   ----------------------------------------------------------------------
   Ran 0 tests in 0.000s

   OK
   I: pybuild base:170: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build;
   python3.4 -m unittest discover -v

   ----------------------------------------------------------------------
   Ran 0 tests in 0.000s

   OK
   I: pybuild base:170: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build;
   python3.5 -m unittest discover -v
   ajax_select (unittest.loader._FailedTest) ... ERROR

So it looks like it can't find the tests under Python 2.7 or Python 3.4,
so it use to work, however under Python 3.5 it now does find the tests
and they fail.

This left me wondering:

* Why does it not find the tests under Python 2.7, 3.4? What is
  different about Python 3.5 that it does?
* Why is Python 3.4 still relevant? Hasn't 3.5 replaced 3.4? Why is it
  being tested by pybuild?

Regards


Reply to: