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 asmeurer
Recipients abarry, asmeurer, ncoghlan, r.david.murray, rhettinger, serhiy.storchaka
Date 2019-06-14.21:45:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560548733.59.0.509162104675.issue32912@roundup.psfhosted.org>
In-reply-to
Content
I agree. Please someone else do that. I don't know what already has issues and I unfortunately don't have time right now to help out with any of this. 

I simply mentioned all these things as arguments why Python should not (yet) make these warnings errors, which is the point of this issue. 

Also, for the pyparsing example, you would have gotten lucky because it also contained \w, which is not a valid escape. If it didn't, you wouldn't be warned. So clearly this will help things, but it will also be good to have linting tools that, for example, warn about any escape sequences inside docstrings.
History
Date User Action Args
2019-06-14 21:45:33asmeurersetrecipients: + asmeurer, rhettinger, ncoghlan, r.david.murray, serhiy.storchaka, abarry
2019-06-14 21:45:33asmeurersetmessageid: <1560548733.59.0.509162104675.issue32912@roundup.psfhosted.org>
2019-06-14 21:45:33asmeurerlinkissue32912 messages
2019-06-14 21:45:33asmeurercreate