➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Incorrect documentation of raw unidaq string literals
Type: Stage:
Components: Documentation Versions: Python 2.5
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: georg.brandl, mhagger
Priority: normal Keywords:

Created on 2005-11-17 15:53 by mhagger, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg26897 - (view) Author: Michael Haggerty (mhagger) Date: 2005-11-17 15:53 
In the Python Reference Manual, section 2.4.1 (String
literals), the last paragraph contains the sentence:

> When an "r" or "R" prefix is used in conjunction with
> a "u" or "U" prefix, then the \uXXXX escape sequence
> is processed while all other backslashes are left in
> the string.

I believe this is incorrect; \UXXXXXXXX sequences also
seem to be processed (at least in Python 2.3.5 and
2.4.1), and it is also logical that they should be
processed.  The required change to the text is obvious:

When an "r" or "R" prefix is used in conjunction with a
"u" or "U" prefix, then the \uXXXX and \UXXXXXXXX
escape sequences are processed while all other
backslashes are left in the string.
msg26898 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2005-11-22 19:25 
Logged In: YES 
user_id=1188172

Thanks! Corrected in revisions 41512 and 41513 (2.4).
History
Date User Action Args
2022-04-11 14:56:14adminsetgithub: 42602
2005-11-17 15:53:03mhaggercreate