summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwulmer <wulmer@users.noreply.github.com>2023-07-22 16:39:46 (GMT)
committerGitHub <noreply@github.com>2023-07-22 16:39:46 (GMT)
commitb71144193b5e7aec022a946a2e36f902280d7c30 (patch)
tree21f39b43fe1d1fa4401b6fc5c5567574e57e15b7
parentc332117b522df8b7aaf5cde81f965405dbb4ae7a (diff)
downloadcpython-b71144193b5e7aec022a946a2e36f902280d7c30.zip
cpython-b71144193b5e7aec022a946a2e36f902280d7c30.tar.gz
cpython-b71144193b5e7aec022a946a2e36f902280d7c30.tar.bz2
[3.11] Fix Sphinx warnings in `re` module docs (GH-107044). (#107055)
(cherry picked from commit 149748ea4f552e6fe43a1d6d69bd65910a7c4813)
-rw-r--r--Doc/library/re.rst23
1 files changed, 18 insertions, 5 deletions
diff --git a/Doc/library/re.rst b/Doc/library/re.rst
index 1f42cd2..798b56a 100644
--- a/Doc/library/re.rst
+++ b/Doc/library/re.rst
@@ -500,6 +500,8 @@ The special characters are:
(``b'\x00'``-``b'\x7f'``) in :class:`bytes` replacement strings.
+.. _re-special-sequences:
+
The special sequences consist of ``'\'`` and a character from the list below.
If the ordinary character is not an ASCII digit or an ASCII letter, then the
resulting RE will match the second character. For example, ``\$`` matches the
@@ -778,6 +780,17 @@ Flags
Corresponds to the inline flag ``(?s)``.
+.. data:: U
+ UNICODE
+
+ In Python 2, this flag made :ref:`special sequences <re-special-sequences>`
+ include Unicode characters in matches. Since Python 3, Unicode characters
+ are matched by default.
+
+ See :const:`A` for restricting matching on ASCII characters instead.
+
+ This flag is only kept for backward compatibility.
+
.. data:: X
VERBOSE
@@ -1518,14 +1531,14 @@ Simulating scanf()
.. index:: single: scanf()
-Python does not currently have an equivalent to :c:func:`scanf`. Regular
+Python does not currently have an equivalent to :c:func:`!scanf`. Regular
expressions are generally more powerful, though also more verbose, than
-:c:func:`scanf` format strings. The table below offers some more-or-less
-equivalent mappings between :c:func:`scanf` format tokens and regular
+:c:func:`!scanf` format strings. The table below offers some more-or-less
+equivalent mappings between :c:func:`!scanf` format tokens and regular
expressions.
+--------------------------------+---------------------------------------------+
-| :c:func:`scanf` Token | Regular Expression |
+| :c:func:`!scanf` Token | Regular Expression |
+================================+=============================================+
| ``%c`` | ``.`` |
+--------------------------------+---------------------------------------------+
@@ -1550,7 +1563,7 @@ To extract the filename and numbers from a string like ::
/usr/sbin/sendmail - 0 errors, 4 warnings
-you would use a :c:func:`scanf` format like ::
+you would use a :c:func:`!scanf` format like ::
%s - %d errors, %d warnings