Author terry.reedy
Recipients Saimadhav.Heblikar, jesstess, python-dev, taleinat, terry.reedy
Date 2014-06-16.23:17:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Attached is the 3.4 patch as pushed. The main 'invisible' change, other than the review comment, was to create the code string just once.

I discovered that the earlier version had a bug in saying 'ok' to the 3.x HyperParser bug of no longer recognizing 'False', etc, as identifiers due to being made keywords. The buggy test properly failed on 2.7. I did the easy fix and split the bad test into two.

Since the 2.7 and 3.x versions of HyperParser were identical before the fix, the 3.x version must also not recognize the new ... Ellipsis literal. Tal, do you think doing so would be sensibly possible? (IE, would it be worth a new issue?)
  x = ...
are all legal 3.x expressions.
Date User Action Args
2014-06-16 23:17:46terry.reedysetrecipients: + terry.reedy, taleinat, jesstess, python-dev, Saimadhav.Heblikar
2014-06-16 23:17:46terry.reedysetmessageid: <>
2014-06-16 23:17:46terry.reedylinkissue21686 messages
2014-06-16 23:17:46terry.reedycreate