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 terry.reedy
Recipients JNCressey, epaine, eric.smith, pablogsal, terry.reedy
Date 2021-03-23.02:11:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1616465473.97.0.136643011299.issue41064@roundup.psfhosted.org>
In-reply-to
Content
Cressey noted both a compile and IDLE Shell issue.  They must be handled separately by different people in separate bpo issues.

The first is about the helpful versus less helpful SyntaxError messages in the following (master compiled today).

>>> f'{*x}'
  File "<stdin>", line 1
    (*x)
     ^
SyntaxError: f-string: can't use starred expression here
>>> f'{**x}'
  File "<stdin>", line 1
    (**x)
     ^
SyntaxError: f-string: invalid syntax

The request is make the 2nd message the same or like the 1st.  Seems like it should be possible.  I am limiting this bpo issue to this request and opened #43600 for fixing IDLE's highlight location.

Pablo, I leave it to you to handle the message enhancement request.  Do you know if there is any other situation like this in which the compiled text is not the input code?
History
Date User Action Args
2021-03-23 02:11:14terry.reedysetrecipients: + terry.reedy, eric.smith, pablogsal, epaine, JNCressey
2021-03-23 02:11:13terry.reedysetmessageid: <1616465473.97.0.136643011299.issue41064@roundup.psfhosted.org>
2021-03-23 02:11:13terry.reedylinkissue41064 messages
2021-03-23 02:11:13terry.reedycreate