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 loganasherjones
Recipients berker.peksag, eric.smith, loganasherjones, remi.lapeyre, serhiy.storchaka
Date 2019-05-06.19:56:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1557172582.37.0.177425088766.issue28002@roundup.psfhosted.org>
In-reply-to
Content
After speaking with Lukasz about this, it seems like the unparser is using the normal unicode repr to determine what should be returned. The default unicode repr will escape quotes if necessary. This is not allowed for f-strings and is the root cause of the problem. 
 
One way to solve this is to add a flag to the unicode_repr function to determine whether or not we need to allow triple quotes in the output of the repr. By default this will be false and will use backslashes, but the ast_unparse will use true for this.
History
Date User Action Args
2019-05-06 19:56:22loganasherjonessetrecipients: + loganasherjones, eric.smith, berker.peksag, serhiy.storchaka, remi.lapeyre
2019-05-06 19:56:22loganasherjonessetmessageid: <1557172582.37.0.177425088766.issue28002@roundup.psfhosted.org>
2019-05-06 19:56:22loganasherjoneslinkissue28002 messages
2019-05-06 19:56:22loganasherjonescreate