>>>>> "BAW" == Barry A Warsaw <barry@python.org> writes:
BAW> before I checked them in, but on my home machine now I see
BAW> failures for test_grammar, test_strptime, and test_tokenize
BAW> (and test_linuxaudiodev but that's always failed for me). I
BAW> definitely don't see the other failures that Skip reports.
The test_tokenize failure was easy, the output file had changed.
The test_grammar failures make sense given the changing semantics of
those constants. I've checked in a change that basically commented
the hex -1 and oct -1 tests since those seem to be testing something
that won't be true. Someone should double check that this is the
right fix.
The test_strptime failure has "gone away". It was:
test test_strptime failed -- Traceback (most recent call last):
File "/home/barry/projects/python/Lib/test/test_strptime.py", line 176, in test_hour
self.failUnless(strp_output[3] == self.time_tuple[3], "testing of '%%I %%p' directive failed; '%s' -> %s != %s" % (strf_output, strp_output[3], self.time_tuple[3]))
File "/home/barry/projects/python/Lib/unittest.py", line 268, in failUnless
if not expr: raise self.failureException, msg
AssertionError: testing of '%I %p' directive failed; '12 PM' -> 24 != 12
I don't get why this was failing and now is not, but don't have time
right now to look at it.
I now have no unexpected skips or failures.
-Barry
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