py3flakes test suite failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Pyflakes |
Invalid
|
Undecided
|
Unassigned |
Bug Description
=======
FAIL: test_invalidEscape (pyflakes.
-------
Traceback (most recent call last):
File "/home/
sourcePath, [decoding_error])
File "/home/
(count, err.getvalue()), (len(errorList), ''.join(
AssertionError: Tuples differ: (1, "/tmp/tmpuzz1ow:1: (unicod... != (1, "/tmp/tmpuzz1ow:1: (unicod...
First differing element 1:
/tmp/tmpuzz1ow:1: (unicode error) 'unicodeescape' codec can't decode bytes in position 0-1: truncated \xXX escape
foo = '\xyz'
^
/tmp/tmpuzz1ow:1: (unicode error) 'unicodeescape' codec can't decode bytes in position 0-2: truncated \xXX escape
foo = '\xyz'
^
(1,
- "/tmp/tmpuzz1ow:1: (unicode error) 'unicodeescape' codec can't decode bytes in position 0-1: truncated \\xXX escape\nfoo = '\\xyz'\n ^\n")
? ^
+ "/tmp/tmpuzz1ow:1: (unicode error) 'unicodeescape' codec can't decode bytes in position 0-2: truncated \\xXX escape\nfoo = '\\xyz'\n ^\n")
? ^
-------
Ran 221 tests in 0.314s
FAILED (failures=1, skipped=8)
When run as:
python3.3 -m unittest discover
summary: |
- test suite failure + py3flakes test suite failure |
Changed in pyflakes: | |
status: | New → Incomplete |
Thanks for the report.
It's weird that this failure was not seen on the Travis builder https:/ /travis- ci.org/ pyflakes/ pyflakes/ builds/ 4454384 unittest2py3k packages to use the same features for older versions of Python.
The difference is that it uses the unittest2/
I just did the "python -m unittest discover" in a checkout of the repository, with Python 3.3, and no failure.