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 ncoghlan
Recipients Tim.Graham, abarry, brett.cannon, eric.smith, martin.panter, ncoghlan, ned.deily, r.david.murray, rhettinger, serhiy.storchaka, yan12125, yselivanov
Date 2016-09-16.02:55:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I've added Eric Smith to the nosy list as well, as he's been working on that part of the compilation pipeline for the f-string implementation.

Eric, the context here is that the new deprecation warning for unknown escapes is currently being misattributed to the code doing the compilation rather than to the code containing the offending (non-)escape sequence.

That's making it difficult for folks to act effectively on the warnings when they receive them, and also poses problems for correctly filtering out warnings coming from code in dependencies rather than an application's own code.
Date User Action Args
2016-09-16 02:55:12ncoghlansetrecipients: + ncoghlan, brett.cannon, rhettinger, eric.smith, ned.deily, r.david.murray, martin.panter, serhiy.storchaka, yselivanov, Tim.Graham, yan12125, abarry
2016-09-16 02:55:12ncoghlansetmessageid: <>
2016-09-16 02:55:12ncoghlanlinkissue28128 messages
2016-09-16 02:55:12ncoghlancreate