2000-08-21 09:37:45 -04:00
|
|
|
|
PEP: 223
|
|
|
|
|
|
Title: Change the Meaning of \x Escapes
|
|
|
|
|
|
Version: $Revision$
|
|
|
|
|
|
Author: tpeters@beopen.com (Tim Peters)
|
2000-08-22 00:42:19 -04:00
|
|
|
|
Python-Version: 2.0
|
2000-08-21 09:37:45 -04:00
|
|
|
|
Status: Draft
|
|
|
|
|
|
Created: 20-Aug-2000
|
2000-08-22 00:42:19 -04:00
|
|
|
|
Post-History:
|
2000-08-21 09:37:45 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Abstract
|
|
|
|
|
|
|
|
|
|
|
|
Change \x escapes, in both 8-bit and Unicode strings, to consume
|
|
|
|
|
|
exactly the two hex digits following. The proposal views this as
|
|
|
|
|
|
correcting an original design flaw, leading to clearer expression
|
|
|
|
|
|
in all flavors of string, a cleaner Unicode story, better
|
|
|
|
|
|
compatibility with Perl regular expressions, and with minimal risk
|
|
|
|
|
|
to existing code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Local Variables:
|
|
|
|
|
|
mode: indented-text
|
|
|
|
|
|
indent-tabs-mode: nil
|
|
|
|
|
|
End:
|
