mirror of
https://github.com/python/cpython.git
synced 2025-10-21 22:22:48 +00:00
bpo-36256: Fix bug in parsermodule when parsing if statements (GH-12477)
bpo-36256: Fix bug in parsermodule when parsing if statements In the parser module, when validating nodes before starting the parsing with to create a ST in "parser_newstobject" there is a problem that appears when two arcs in the same DFA state has transitions with labels with the same type. For example, the DFA for if_stmt has a state with two labels with the same type: "elif" and "else" (type NAME). The algorithm tries one by one the arcs until the label that starts the arc transition has a label with the same type of the current child label we are trying to accept. In this case, the arc for "elif" comes before the arc for "else"and passes this test (because the current child label is "else" and has the same type as "elif"). This lead to expecting a namedexpr_test (305) instead of a colon (11). The solution is to compare also the string representation (in case there is one) of the labels to see if the transition that we have is the correct one.
This commit is contained in:
parent
aedc273fd9
commit
9a0000d15d
3 changed files with 23 additions and 5 deletions
|
@ -319,6 +319,10 @@ class RoundtripLegalSyntaxTestCase(unittest.TestCase):
|
|||
self.check_suite("try: pass\nexcept: pass\nelse: pass\n"
|
||||
"finally: pass\n")
|
||||
|
||||
def test_if_stmt(self):
|
||||
self.check_suite("if True:\n pass\nelse:\n pass\n")
|
||||
self.check_suite("if True:\n pass\nelif True:\n pass\nelse:\n pass\n")
|
||||
|
||||
def test_position(self):
|
||||
# An absolutely minimal test of position information. Better
|
||||
# tests would be a big project.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue