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 lukasz.langa
Recipients benjamin.peterson, eli.bendersky, jab, josephgordon, lukasz.langa, ned.deily, serhiy.storchaka
Date 2017-03-10.08:29:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489134557.18.0.526472427393.issue23894@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think we'll fix it for 3.5 anymore but it's definitely worth doing so for 3.6.1.

Ned, I have a patch, will upload momentarily. I'd like this to go in 3.6.1 since without it fixed tools depending on lib2to3 will crash seeing f-strings. This includes YAPF, a pretty widely used auto-formatter for Python code. The fix is relatively trivial. What do you think?
History
Date User Action Args
2017-03-10 08:29:17lukasz.langasetrecipients: + lukasz.langa, benjamin.peterson, ned.deily, eli.bendersky, jab, serhiy.storchaka, josephgordon
2017-03-10 08:29:17lukasz.langasetmessageid: <1489134557.18.0.526472427393.issue23894@psf.upfronthosting.co.za>
2017-03-10 08:29:17lukasz.langalinkissue23894 messages
2017-03-10 08:29:16lukasz.langacreate