summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGeorg Brandl <georg@python.org>2005-11-22 19:24:23 (GMT)
committerGeorg Brandl <georg@python.org>2005-11-22 19:24:23 (GMT)
commit50541d16481c771af1c70c6eb8137fa4657dcdae (patch)
treed70c42f3a59f93b5b046f2e9d3624ac8b7e3f3c7
parenta4e9aa6f65f75c209f7fb68ecea1c6662b0d4ead (diff)
downloadcpython-50541d16481c771af1c70c6eb8137fa4657dcdae.zip
cpython-50541d16481c771af1c70c6eb8137fa4657dcdae.tar.gz
cpython-50541d16481c771af1c70c6eb8137fa4657dcdae.tar.bz2
Bug #1359035: Doc: Uxxxxxxxx escapes are interpreted in raw unicode literals.
-rw-r--r--Doc/ref/ref2.tex5
1 files changed, 3 insertions, 2 deletions
diff --git a/Doc/ref/ref2.tex b/Doc/ref/ref2.tex
index 950a732..af79e4d 100644
--- a/Doc/ref/ref2.tex
+++ b/Doc/ref/ref2.tex
@@ -514,8 +514,9 @@ as part of the string, \emph{not} as a line continuation.
When an \character{r} or \character{R} prefix is used in conjunction
with a \character{u} or \character{U} prefix, then the \code{\e uXXXX}
-escape sequence is processed while \emph{all other backslashes are
-left in the string}. For example, the string literal
+and \code{\e UXXXXXXXX} escape sequences are processed while
+\emph{all other backslashes are left in the string}.
+For example, the string literal
\code{ur"\e{}u0062\e n"} consists of three Unicode characters: `LATIN
SMALL LETTER B', `REVERSE SOLIDUS', and `LATIN SMALL LETTER N'.
Backslashes can be escaped with a preceding backslash; however, both