This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zach.ware
Recipients Chema Cortés, Guido Treutwein, Yury.Selivanov, docs@python, rjordens, serhiy.storchaka, yselivanov, zach.ware
Date 2016-05-06.04:45:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1462509944.3.0.95226144861.issue26156@psf.upfronthosting.co.za>
In-reply-to
Content
I agree that what is currently in the docs is technically correct.  The section on the power operator:

   power ::=  await ["**" u_expr]

should be read as:

   power ::=  (["await"] primary) ["**" u_expr]

just as the definition of 'u_expr' below should be read as:

   u_expr ::=  (await ["**" u_expr]) | "-" u_expr | "+" u_expr | "~" u_expr

and 'await' should be read as:

   await ::= ["await"] (atom | attributeref | subscription | slicing | call)

Each definition builds upon previous ones.

However, it is confusing.  Could a name other than "await" be used, since "await" is easily confused with the keyword await?
History
Date User Action Args
2016-05-06 04:45:44zach.waresetrecipients: + zach.ware, docs@python, Yury.Selivanov, serhiy.storchaka, yselivanov, rjordens, Chema Cortés, Guido Treutwein
2016-05-06 04:45:44zach.waresetmessageid: <1462509944.3.0.95226144861.issue26156@psf.upfronthosting.co.za>
2016-05-06 04:45:44zach.warelinkissue26156 messages
2016-05-06 04:45:43zach.warecreate