[issue32626] Subscript unpacking raises SyntaxError

Serhiy Storchaka added the comment: Issue32117 looks considering a more general question about iterable unpacking. -- nosy: +serhiy.storchaka resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Tuple unpacking in return and yield statements

[issue32626] Subscript unpacking raises SyntaxError

Neil Girdhar added the comment: This came up already on python-ideas: https://groups.google.com/forum/#!topic/python-ideas/YOpT9fDQyFk I think this was an oversight, and I'm with Ben that it's unexpected. That said, this is usually the kind of thing that Guido likes to comment on. My sugge

[issue32626] Subscript unpacking raises SyntaxError

Ben Burrill added the comment: Yeah, but in this case, you don't need parentheses unless you use unpacking. That is unexpected behavior. -- ___ Python tracker ___ ___

[issue32626] Subscript unpacking raises SyntaxError

Terry J. Reedy added the comment: Tuples often need parentheses when embedded in expressions. So often that beginners often think that they are required. I believe this should be closed as 'not a bug'. I nosied the two authors of the implementation for their opinion. -- nosy: +Jos

[issue32626] Subscript unpacking raises SyntaxError

New submission from Ben Burrill : PEP 448 defines unpacking generalizations for tuples. However, this does not currently work for subscripted tuples that are not delimited by parentheses. Current behavior (Tested on 3.6/3.7a4): >>> class Subscriptable: ... def __getitem__(self, item): ...