[3.8] bpo-32912: Revert warnings for invalid escape sequences. by serhiy-storchaka · Pull Request #15142 · python/cpython

@serhiy-storchaka

DeprecationWarning will continue to be emitted for invalid
escape sequences in string and bytes literals in 3.8.
SyntaxWarning will be emitted in 3.9.

jdemeyer

@serhiy-storchaka

rhettinger

@gpshead

and mention that SyntaxError will happen after SyntaxWarning.  we're being non-specific on purpose here as we haven't worked out the plan to make this happen without causing end user pain yet.  right now most code owners do not see the DeprecationWarning but when turned into a SyntaxWarning, _users_ of libraries see it more often than owners.  So it is a negative experience all around.

CuriousLearner

miss-islington pushed a commit that referenced this pull request

Aug 10, 2019
DeprecationWarning will continue to be emitted for invalid escape
sequences in string and bytes literals just as it did in 3.7.

SyntaxWarning may be emitted in the future. But per mailing list
discussion, we don't yet know when because we haven't settled on how to
do so in a non-disruptive manner.

(Applies 4c5b6ba to the master branch).
(This is #15142 for master/3.9)


https://bugs.python.org/issue32912



Automerge-Triggered-By: @gpshead

lisroach pushed a commit to lisroach/cpython that referenced this pull request

Sep 10, 2019
…H-15195)

DeprecationWarning will continue to be emitted for invalid escape
sequences in string and bytes literals just as it did in 3.7.

SyntaxWarning may be emitted in the future. But per mailing list
discussion, we don't yet know when because we haven't settled on how to
do so in a non-disruptive manner.

(Applies 4c5b6ba to the master branch).
(This is python#15142 for master/3.9)


https://bugs.python.org/issue32912



Automerge-Triggered-By: @gpshead

DinoV pushed a commit to DinoV/cpython that referenced this pull request

Jan 14, 2020
…H-15195)

DeprecationWarning will continue to be emitted for invalid escape
sequences in string and bytes literals just as it did in 3.7.

SyntaxWarning may be emitted in the future. But per mailing list
discussion, we don't yet know when because we haven't settled on how to
do so in a non-disruptive manner.

(Applies 4c5b6ba to the master branch).
(This is python#15142 for master/3.9)


https://bugs.python.org/issue32912



Automerge-Triggered-By: @gpshead

websurfer5 pushed a commit to websurfer5/cpython that referenced this pull request

Jul 20, 2020
…H-15195)

DeprecationWarning will continue to be emitted for invalid escape
sequences in string and bytes literals just as it did in 3.7.

SyntaxWarning may be emitted in the future. But per mailing list
discussion, we don't yet know when because we haven't settled on how to
do so in a non-disruptive manner.

(Applies 4c5b6ba to the master branch).
(This is python#15142 for master/3.9)


https://bugs.python.org/issue32912



Automerge-Triggered-By: @gpshead

@Vgr255 Vgr255 mannequin mentioned this pull request

Nov 2, 2022