On Sat, 10 Aug 2019 at 01:44, Guido van Rossum <guido@python.org> wrote:
This discussion looks like there's no end in sight. Maybe the Steering Council should take a vote?
I find the "Our deprecation warnings were even less visible than normal" argument for extending the deprecation period compelling. I also think the UX of the warning itself could be reviewed to provide a more explicit nudge towards using raw strings when folks want to allow arbitrary embedded backslashes. Consider: SyntaxWarning: invalid escape sequence \, vs something like: SyntaxWarning: invalid escape sequence \, (Note: adding the raw string literal prefix, r, will accept all non-trailing backslashes) After all, the habit we're trying to encourage is "If I want to include backslashes without escaping them all, I should use a raw string", not "I should memorize the entire set of valid escape sequences" or even "I should always escape backslashes". Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia