[issue4857] syntax: no unpacking in augassign

Georg Brandl added the comment: Fixed in r68725. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue4857] syntax: no unpacking in augassign

Terry J. Reedy added the comment: The grammar in the doc is not the one used to generate the parser/compiler. The former is meant to be easier for humans to read, the latter easier for the parser generator. Neither completely embody Python's syntax rules. Additional restrictions may be applie

[issue4857] syntax: no unpacking in augassign

STINNER Victor added the comment: Oh yes! I didn't see "(" target_list ")" | "[" target_list "]", sorry. ___ Python tracker ___ ___ Python-bugs

[issue4857] syntax: no unpacking in augassign

jura added the comment: Yes, but target ::= identifier | "(" target_list ")" | ... so (x,y) seems to be a valid target. ___ Python tracker ___

[issue4857] syntax: no unpacking in augassign

STINNER Victor added the comment: Extract of the grammar: target ::= identifier | ... target_list ::= target ("," target)* [","] assignment_stmt ::= (target_list "=")+ ... augmented_assignment_stmt ::= target augop ... augop ::= "+=" | ... So ther

[issue4857] syntax: no unpacking in augassign

New submission from jura : the following code produces syntax error: >>> (x, y) += 1 While this is documented in http://docs.python.org/3.0/reference/simple_stmts.html#augmented-assignment-statements ("An augmented assignment evaluates the target (which, unlike normal аssignment statements, canno