Message276720
Personally I'd be fine with only one warning, reporting the first invalid escape. Presumably the string would be checked as a whole, or would get an r prefix. Patch seems like a good start; bytes would also need updating in that regard. Don't worry too much about the details, we can iron that out later :)
Also yeah, the fact that warnings are triggered at compile time results in surprising behaviour even for me. I'm liking the idea of a DeprecatedSyntaxWarning more.
I'll try to get some work done in that regard by the end of next week, but life's been somewhat busy so I can't give any guarantees. Thank you for your patch draft though, it helps me to figure out how I should tackle this! |
|
Date |
User |
Action |
Args |
2016-09-16 14:34:26 | abarry | set | recipients:
+ abarry, brett.cannon, rhettinger, ncoghlan, eric.smith, ned.deily, r.david.murray, martin.panter, serhiy.storchaka, yselivanov, Tim.Graham, yan12125 |
2016-09-16 14:34:26 | abarry | set | messageid: <1474036466.45.0.0456320227121.issue28128@psf.upfronthosting.co.za> |
2016-09-16 14:34:26 | abarry | link | issue28128 messages |
2016-09-16 14:34:25 | abarry | create | |
|