Serhiy Storchaka added the comment:
Following patch just raises SyntaxError if DeprecationWarning was raised as
error. Still needed tests for this.
> Also, you'll note that with or without your patch, you get the same behavior.
Not the same. New warnings contain correct information about a file and a line.
$ ./python-unpatched -Wa escape_warning.py
_frozen_importlib:205: DeprecationWarning: invalid escape sequence '\d'
\d
$ ./python-patched -Wa escape_warning.py
/home/serhiy/py/cpython-3.6/bad_escape.py:2: DeprecationWarning: invalid escape
sequence \d
print('\d')
\d
$ ./python-unpatched -We escape_warning.py
Traceback (most recent call last):
File "escape_warning.py", line 1, in <module>
import bad_escape
DeprecationWarning: invalid escape sequence '\d'
$ ./python-patched -We escape_warning.py
Traceback (most recent call last):
File "escape_warning.py", line 1, in <module>
import bad_escape
File "/home/serhiy/py/cpython-3.6/bad_escape.py", line 2
print('\d')
^
SyntaxError: invalid escape sequence \d
----------
Added file: http://bugs.python.org/file45293/28128-7.diff
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28128>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
