[issue3558] Operator precedence misdocumented

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

[issue3558] Operator precedence misdocumented

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: I am reopening because my suggested fix was wrong. As pointed out by Fredrik Lundh on PyDev the next day, quoting from the grammar, attributes, subscriptions, slicing, and call have the *same* precedence. I thought I posted his comment and an

[issue3558] Operator precedence misdocumented

Georg Brandl <[EMAIL PROTECTED]> added the comment: Thanks, moved attribute reference to the appropriate place in r65693. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3558] Operator precedence misdocumented

New submission from Terry J. Reedy <[EMAIL PROTECTED]>: Reference/Expressions/Primaries: "Primaries represent the most tightly bound operations of the language. Their syntax is: primary ::= atom | attributeref | subscription | slicing | call" This (along with the fact that all sections after 'c