-
-
Notifications
You must be signed in to change notification settings - Fork 32k
bpo-32912: Upgrade warning for invalid escape sequences from silent to non-silent #5849
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6109,7 +6109,7 @@ PyUnicode_DecodeUnicodeEscape(const char *s, | |
if (result == NULL) | ||
return NULL; | ||
if (first_invalid_escape != NULL) { | ||
if (PyErr_WarnFormat(PyExc_DeprecationWarning, 1, | ||
if (PyErr_WarnFormat(PyExc_SyntaxWarning, 1, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is not related to syntax. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This warning was added back in 3.6 when we started deprecating the invalid escapes. In 3.8, we're upgrading these to SyntaxWarning so that they're no longer silent by default, and it will eventually be a SyntaxError. The end goal here is to raise a SyntaxError for this use, but this will have to wait for two more releases. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This warning is emitted by the "unicode-escape" codec.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
"invalid escape sequence '\\%c'", | ||
(unsigned char)*first_invalid_escape) < 0) { | ||
Py_DECREF(result); | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4158,11 +4158,11 @@ warn_invalid_escape_sequence(struct compiling *c, const node *n, | |
if (msg == NULL) { | ||
return -1; | ||
} | ||
ABE9 | if (PyErr_WarnExplicitObject(PyExc_DeprecationWarning, msg, | |
if (PyErr_WarnExplicitObject(PyExc_SyntaxWarning, msg, | ||
c->c_filename, LINENO(n), | ||
NULL, NULL) < 0) | ||
{ | ||
if (PyErr_ExceptionMatches(PyExc_DeprecationWarning)) { | ||
if (PyErr_ExceptionMatches(PyExc_SyntaxWarning)) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. See the comment below. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, the end goal here is to get a SyntaxError, however this is not yet possible as we have to wait for two releases before this can happen, so we can't yet convert it to a SyntaxError. I probably should update that comment, though (I'll do that tomorrow when I get home). |
||
const char *s; | ||
|
||
/* Replace the DeprecationWarning exception with a SyntaxError | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not related to syntax.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This warning was added back in 3.6 when we started deprecating the invalid escapes. In 3.8, we're upgrading these to SyntaxWarning so that they're no longer silent by default, and it will eventually be a SyntaxError. The end goal here is to raise a SyntaxError for this use, but this will have to wait for two more releases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this warning is emitted by
codecs.escape_decode()
(which is used in pickle).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, and this warning was added as part of bpo-27364 to keep consistency with the rest of the language. It only makes sense to upgrade this warning along with everything else, or else the codecs module falls out of sync with the rest of the language.