[issue32603] Deprecation warning on strings used in re module

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue32603] Deprecation warning on strings used in re module

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +5102 stage: -> patch review ___ Python tracker ___ ___ Python-

[issue32603] Deprecation warning on strings used in re module

Pablo Galindo Salgado added the comment: +1 to this. I have seen a lot of regular expressions not using raw strings that makes use of "\d" and friends. I will work on a patch to the docs if that's ok. -- nosy: +pablogsal ___ Python tracker

[issue32603] Deprecation warning on strings used in re module

Steven D'Aprano added the comment: I agree with Cheryl that it would be a good idea to mention this change in the re docs, since regexes are especially likely to run into this issue. -- nosy: +steven.daprano ___ Python tracker

[issue32603] Deprecation warning on strings used in re module

Cheryl Sabella added the comment: Thank you, Zach. There was some mention of regular expressions in #27364, but I'm still wondering if the DeprecationWarning should be mentioned on the re doc page and if there should be stronger language about using raw strings. Thanks! --

[issue32603] Deprecation warning on strings used in re module

Zachary Ware added the comment: This is actually combination of a deprecation in in 3.6's string literals (not related to the re module), documented here: https://docs.python.org/dev/whatsnew/3.6.html#deprecated-python-behavior (see issue27364) and showing DeprecationWarning in the REPL by de

[issue32603] Deprecation warning on strings used in re module

New submission from Cheryl Sabella : I apologize if this is a duplicate question, but I couldn't find another issue about this. It's hard to search on 're'. In 3.7, I get a deprecation warning when using a regular string with re escape characters: >>> s = '123abcd' >>> re.findall('\d', s) :1: