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 eric.smith
Recipients Tim.Graham, abarry, eric.smith, ezio.melotti, martin.panter, ncoghlan, ned.deily, petr.viktorin, r.david.murray, rhettinger, serhiy.storchaka, yan12125, yselivanov
Date 2016-10-31.11:57:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

I had tried this approach earlier, but it doesn't work. With your -5.diff patch, the output is (using Nick's test case):

$ rm -rf __pycache__/ ; ./python -Werror 
Traceback (most recent call last):
  File "", line 1, in <module>
    import bad_escape
DeprecationWarning: invalid escape sequence \d

With my -4.diff patch, you get the desired full stack trace:

$ rm -rf __pycache__/ ; ./python -Wall 
Traceback (most recent call last):
  File "", line 1, in <module>
    import bad_escape
  File "/home/eric/local/python/cpython/", line 1
SyntaxError: invalid escape sequence \d

The trick is: how to make the DeprecationWarning version produce output similar to the SyntaxError case? Note that with DeprecationWarning, you don't see the line in that actually contains the string with the invalid escape.
Date User Action Args
2016-10-31 11:57:36eric.smithsetrecipients: + eric.smith, rhettinger, ncoghlan, ned.deily, ezio.melotti, r.david.murray, petr.viktorin, martin.panter, serhiy.storchaka, yselivanov, Tim.Graham, yan12125, abarry
2016-10-31 11:57:36eric.smithsetmessageid: <>
2016-10-31 11:57:36eric.smithlinkissue28128 messages
2016-10-31 11:57:36eric.smithcreate