36e28b331a
This change addresses the bug where inaccurate line numbers / ranges are displayed when an issue is detected in a multiline statement. There's been a Python issue open since 2012 about this: http://bugs.python.org/issue16806 Two main parts to the commit: - Modify StatementBuffer so get_next() will allow lookahead without popping the item off the buffer. - Add cleverness to visit() so if it does come across a multiline statement, it updates the context linerange based on information pulled out of the StatementBuffer. Also of note, the commit includes several new tests for fix verification. Seemingly non-deterministic test results were driving me batty until the need to move the BanditResultStore 'resstore = OrderedDict()' call from class-level to object instantion became obvious. Change-Id: I7dd4c563f6b2f8a103224854f0709068af093a73 Closes-Bug: 1467636 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| test_basic.py | ||
| test_functional.py | ||
| test_node_visitor.py | ||
| test_util.py | ||