Message312575
This is a follow-up to Issue27364.
Back in Python 3.6, a silent warning was added for all invalid escape sequences in str and bytes. It was suggested that it would remain a silent warning (which still impacts tests, while not visually annoying the average user) for two releases (3.6 and 3.7), then would be upgraded to a non-silent warning for two subsequent releases (3.8 and 3.9) before becoming a full-on syntax error. With the 3.7 feature freeze on and going, I think it's time to evaluate the approach we take for 3.8 :)
I suggest upgrading the DeprecationWarning to a SyntaxWarning, which is visible by default, for 3.8 and 3.9. I have cross-linked #27364 to this issue as well.
-Em |
|
Date |
User |
Action |
Args |
2018-02-22 18:34:57 | abarry | set | recipients:
+ abarry |
2018-02-22 18:34:57 | abarry | set | messageid: <1519324497.82.0.467229070634.issue32912@psf.upfronthosting.co.za> |
2018-02-22 18:34:57 | abarry | link | issue32912 messages |
2018-02-22 18:34:57 | abarry | create | |
|