[Martin v. L=F6wis]
> I don't know. I cannot understand the purpose of _expectations.
If a Python expert for platform sys.platform X would be at all surpri=
sed if
test T got skipped when running the tests on X, then T should not be =
listed
in _expectations[X], else it should be, with disagreements favoring l=
eaving
it out (the disagreeing experts can add a comment to regrtest.py abou=
t why
they disagree, or make regrtest smarter about recognizing when a test=
skip
is expected). I added a couple of the latter to _ExpectedSkips.__ini=
t__:
if not os.path.supports_unicode_filenames:
self.expected.add('test_pep277')
if test_normalization.skip_expected:
self.expected.add('test_normalization')
if test_socket_ssl.skip_expected:
self.expected.add('test_socket_ssl')
but so far nobody else has cared enough to add more of this nature. =
If a
module can't itself tell whether it expects to be skipped, then perha=
ps we
need another "mystery test" category (where mystery =3D=3D we have no=
idea
whether the test should pass -- such tests will always be a source of
confusion).
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4