[issue40199] Invalid escape sequence DeprecationWarnings don't trigger by default

James Gerity added the comment: The cause of DeprecationWarning sometimes [1] not being issued is I believe because in string_parser.c [2] the module is explicitly set to NULL and the filename will be '' or '' or somesuch, which eventually that ends up being normalized to something that

[issue40199] Invalid escape sequence DeprecationWarnings don't trigger by default

Serhiy Storchaka added the comment: Ah, there is a difference between debug and regular builds. I tested with the debug build. -- components: +Interpreter Core -Windows nosy: +ncoghlan, vstinner -paul.moore, steve.dower, tim.golden, zach.ware versions: +Python 3.10, Python 3.11,

[issue40199] Invalid escape sequence DeprecationWarnings don't trigger by default

Aaron Gallagher <_...@habnab.it> added the comment: This is definitely not windows-specific. On macos: $ python3.9 Python 3.9.4 (default, Apr 5 2021, 01:47:16) [Clang 11.0.0 (clang-1100.0.33.17)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> '\s' '\\s'

[issue40199] Invalid escape sequence DeprecationWarnings don't trigger by default

Change by Serhiy Storchaka : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___

[issue40199] Invalid escape sequence DeprecationWarnings don't trigger by default

Terry J. Reedy added the comment: OK, verified issue with installed 3.9.0a5, which must have different warning settings. >From a file, 1 warning. :1: DeprecationWarning: invalid escape sequence \d Interactively, no warning. >>> compile("'\d'", "", "eval") at 0x0263842DFC90, file "",

[issue40199] Invalid escape sequence DeprecationWarnings don't trigger by default

Numerlor added the comment: The newest 64 bit release from python.org via the executable installer. -- ___ Python tracker ___ ___

[issue40199] Invalid escape sequence DeprecationWarnings don't trigger by default

Terry J. Reedy added the comment: On Win 10, with recently compiled 3.7.7+ and 3.9.0a5+, I get 4 warnings also. >>> import warnings >>> compile("'\d'", "", "eval") :1: DeprecationWarning: invalid escape sequence \d :1: DeprecationWarning: invalid escape sequence \d at 0x00A65DC0, file "",

[issue40199] Invalid escape sequence DeprecationWarnings don't trigger by default

Numerlor added the comment: In what environment was that ran in? The issue seems to exist in all the different environments that are easily available to me (win7, win10, linux under docker and on repl.it) -- ___ Python tracker

[issue40199] Invalid escape sequence DeprecationWarnings don't trigger by default

Serhiy Storchaka added the comment: I get it printed two times. Actually I get it printed four times: two time when compile the test script (use r"'\d'" or "'\\d'" to get rid of them), and other two times when call compile() inside a script. $ ./python issue40199.py issue40199.py:3:

[issue40199] Invalid escape sequence DeprecationWarnings don't trigger by default

New submission from Michal Laboš : The current warning filter seems to filter out the compile time DeprecationWarnings that get triggered on invalid escape sequences: import warnings compile("'\d'", "", "eval") warnings.resetwarnings() compile("'\d'", "", "eval") results in one :1: