Closed 0-wiz-0 closed 2 years ago
Same, as for the fixtures ticket, I'm going to close this unless somebody wants to maintain support for NetBSD.
Do you have any idea how e.g.
AttributeError: 'TestMatchersInterface' object has no attribute 'describe_examples'
could happen, and in particular only on NetBSD?
When not using py-test but python3.7 -m testtools.run testtools.tests.test_suite
, I see:
======================================================================
FAIL: testtools.tests.matchers.test_exception.TestMatchesExceptionInstanceInterface.test__str__
----------------------------------------------------------------------
Traceback (most recent call last):
File "/scratch/devel/py-testtools/work/testtools-2.3.0/testtools/tests/matchers/helpers.py", line 26, in test__str__
self.assertThat(matcher, DocTestMatches(expected))
File "/scratch/devel/py-testtools/work/testtools-2.3.0/testtools/testcase.py", line 498, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: Expected:
MatchesException(Exception('foo',))
Got:
MatchesException(Exception('foo'))
======================================================================
FAIL: testtools.tests.matchers.test_exception.TestMatchesExceptionInstanceInterface.test_describe_difference
----------------------------------------------------------------------
Traceback (most recent call last):
File "/scratch/devel/py-testtools/work/testtools-2.3.0/testtools/tests/matchers/helpers.py", line 33, in test_describe_difference
self.assertEqual(difference, mismatch.describe())
File "/scratch/devel/py-testtools/work/testtools-2.3.0/testtools/testcase.py", line 411, in assertEqual
self.assertThat(observed, matcher, message)
File "/scratch/devel/py-testtools/work/testtools-2.3.0/testtools/testcase.py", line 498, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: !=:
reference = "ValueError('bar',) has different arguments to ValueError('foo',)."
actual = "ValueError('bar') has different arguments to ValueError('foo')."
Btw, the Makefile hardcodes "PYTHON=python" and not all distributions provide an unversioned python binary.
Thats very odd indeed.
re: the python command - this does predate PEP-394, but as we currently target source compat with both python 2 and 3, it is appropriate to continue to default to python. We should probably change that to ?= rather than = though to make it easy for you to supply the python executable you wish to use.
2.4.0 and 2.5.0 have no test failures any longer. Thanks!
2.2.0 has 38 test failures on NetBSD-7.99.59/amd64 with testscenarios-0.5.0, extras-1.0.0, fixtures-3.0.0, mimeparse-0.1.4, unittest2-1.1.0: