bpo-28450: Fix and improve the documentation for unknown escapes in RE. (GH-11920)

This commit is contained in:
Serhiy Storchaka 2019-02-25 17:58:30 +02:00 committed by GitHub
parent 6a44f6eef3
commit a180b007d9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -573,7 +573,8 @@ accepted by the regular expression parser::
only inside character classes.)
``'\u'``, ``'\U'``, and ``'\N'`` escape sequences are only recognized in Unicode
patterns. In bytes patterns they are errors.
patterns. In bytes patterns they are errors. Unknown escapes of ASCII
letters are reserved for future use and treated as errors.
Octal escapes are included in a limited form. If the first digit is a 0, or if
there are three octal digits, it is considered an octal escape. Otherwise, it is
@ -850,7 +851,9 @@ form.
*string* is returned unchanged. *repl* can be a string or a function; if it is
a string, any backslash escapes in it are processed. That is, ``\n`` is
converted to a single newline character, ``\r`` is converted to a carriage return, and
so forth. Unknown escapes such as ``\&`` are left alone. Backreferences, such
so forth. Unknown escapes of ASCII letters are reserved for future use and
treated as errors. Other unknown escapes such as ``\&`` are left alone.
Backreferences, such
as ``\6``, are replaced with the substring matched by group 6 in the pattern.
For example::