Message275757
| Author |
yan12125 |
| Recipients |
abarry, ezio.melotti, gvanrossum, jayvdb, martin.panter, python-dev, r.david.murray, serhiy.storchaka, terry.reedy, vstinner, yan12125, ztane |
| Date |
2016年09月11日.09:35:50 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1473586550.65.0.533717871717.issue27364@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Currently the deprecation message is not so useful when fixing lots of files in a large project. For example, I have two files foo.py and bar.py:
# foo.py
import bar
# bar.py
print('\d')
It gives:
$ python3.6 -W error foo.py
Traceback (most recent call last):
File "foo.py", line 1, in <module>
import bar
DeprecationWarning: invalid escape sequence '\d'
Things are worse when __import__, imp or importlib are involved. I have to add some codes to show which module is imported.
It would be better to have at least filenames and line numbers:
$ ./python -W error foo.py
Traceback (most recent call last):
File "foo.py", line 1, in <module>
import bar
File "/home/yen/Projects/cpython/build/bar.py", line 1
print('\d')
^
SyntaxError: (deprecated usage) invalid escape sequence '\d'
I have a naive try that prints more information. Raising SyntaxError may not be a good idea, anyway. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年09月11日 09:35:50 | yan12125 | set | recipients:
+ yan12125, gvanrossum, terry.reedy, vstinner, ezio.melotti, r.david.murray, python-dev, martin.panter, serhiy.storchaka, ztane, jayvdb, abarry |
| 2016年09月11日 09:35:50 | yan12125 | set | messageid: <1473586550.65.0.533717871717.issue27364@psf.upfronthosting.co.za> |
| 2016年09月11日 09:35:50 | yan12125 | link | issue27364 messages |
| 2016年09月11日 09:35:50 | yan12125 | create |
|