R. David Murray <rdmur...@bitdance.com> added the comment: Hmm. OK, I didn't think that's how we'd defined those terms, but then I don't actually work with the parser much myself :) However, generator expressions are clearly called out as a separate thing. All of the other display types get their own section, so I would think tuple display should too if it really is a syntax unit...but maybe it isn't.
Also, I'm not clear on what 'binding' means in that table entry. I see now why you wanted to say "parenthesized expression", but as far as I can see the previous text is referring to it as an expression list in parenthesis form. That's a bit wordy, which may be why someone used tuple display there. Clearly there is some ambiguity here that it would be nice to resolve, considering this is part of the language spec, but frankly I'm not sure what to suggest. At that level I'm not sure how the "operator precedence" is actually "resolved"...I think it is more a matter of it being implicit in the parsing, but I'm not sure. Like I said, not my area of expertise. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33459> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
