[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Serhiy Storchaka added the comment: New changeset 95fc8e687c487ecf97f4b1b98dfc0c05e3c9cbff by Serhiy Storchaka in branch '3.7': [3.7] bpo-28450: Fix and improve the documentation for unknown escapes in RE. (GH-11920). (GH-12029)

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Change by Serhiy Storchaka : -- pull_requests: +12060 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Serhiy Storchaka added the comment: New changeset a180b007d96fe68b32f11dec720fbd0cd5b6758a by Serhiy Storchaka in branch 'master': bpo-28450: Fix and improve the documentation for unknown escapes in RE. (GH-11920)

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +11945 stage: needs patch -> patch review ___ Python tracker ___

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Serhiy Storchaka added the comment: Barry, could you please improve the documentation about unknown escape sequences in regular expressions? My skills is not enough for this. -- ___ Python tracker

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Ned Deily added the comment: Note that 1b162d6e3d01 in Issue27030 (for 3.6.0rc1) has changed the behavior for re.sub replacement templates to produce a deprecation warning in 3.6 while still being treated as an error in 3.7. -- ___ Python tracker

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Serhiy Storchaka added the comment: I think we should discuss this on Python-Dev. -- ___ Python tracker ___

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Ned Deily added the comment: Where do we stand on this issue? At the moment, 3.6.0 is on track to be released as is. -- nosy: +ned.deily ___ Python tracker

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Changes by Emanuel Barry : -- nosy: +ebarry ___ Python tracker ___ ___ Python-bugs-list

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Barry A. Warsaw added the comment: On Nov 22, 2016, at 07:28 PM, Serhiy Storchaka wrote: >The reason for disallowing some undefined escapes is the same as in pattern >strings: this would allow as to introduce new special escape sequences. I'll note that technically speaking, you can still

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Matthew Barnett added the comment: @Barry: repl already supports some escapes, e.g. \g for named groups, although not \xXX et al, so deprecating unknown escapes like in the pattern makes sense to me. BTW, the regex module already supports \xXX, \N{XXX}, etc. --

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Serhiy Storchaka added the comment: The reason for disallowing some undefined escapes is the same as in pattern strings: this would allow as to introduce new special escape sequences. For example: * \N{...} for named character escape. * Perl and extended PCRE use \L and \U for making lower

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Serhiy Storchaka added the comment: The deprecation was documented in 3.5. https://docs.python.org/3.5/library/re.html#re.sub Deprecated since version 3.5, will be removed in version 3.6: Unknown escapes consist of '\' and ASCII letter now raise a deprecation warning and will be forbidden in

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Barry A. Warsaw added the comment: I disagree that the documentation is at fault. This is known to break existing code, e.g. http://bugs.python.org/msg281496 I think it's not correct to change the documentation but leave the error-raising behavior for 3.6 because the deprecation was never

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Serhiy Storchaka added the comment: Maybe just remove the phrase "Unknown escapes such as \& are left alone"? -- ___ Python tracker ___

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Changes by Serhiy Storchaka : -- components: +Regular Expressions nosy: +ezio.melotti ___ Python tracker ___

[issue28450] Misleading/inaccurate documentation about unknown escape sequences in regular expressions

Serhiy Storchaka added the comment: Thank you for your report Lele. Agreed, the documentation looks misleading. Do you want to provide more clear wording? -- nosy: +Rosuav, mrabarnett, nedbat, serhiy.storchaka stage: -> needs patch title: Misleading/inaccurate documentation about

[issue28450] Misleading/inaccurate documentation about unknown escape sequences

New submission from Lele Gaifax: Python 3.6+ is stricter about escaped sequences in string literals. The documentation need some improvement to clarify the change: for example https://docs.python.org/3.6/library/re.html#re.sub first says that “Unknown escapes such as \& are left alone” then,