diff options
author | Ezio Melotti <ezio.melotti@gmail.com> | 2011-09-28 21:18:19 (GMT) |
---|---|---|
committer | Ezio Melotti <ezio.melotti@gmail.com> | 2011-09-28 21:18:19 (GMT) |
commit | 48a2f8fd972205688a1011348100bdb482c81836 (patch) | |
tree | 09f86d9cdf88c75688bc836c78e54ea88d365371 /Doc/whatsnew | |
parent | 506f5927691e0088adc7ac6e6d7b43ad78f1576b (diff) | |
download | cpython-48a2f8fd972205688a1011348100bdb482c81836.zip cpython-48a2f8fd972205688a1011348100bdb482c81836.tar.gz cpython-48a2f8fd972205688a1011348100bdb482c81836.tar.bz2 |
#13054: sys.maxunicode is now always 0x10FFFF.
Diffstat (limited to 'Doc/whatsnew')
-rw-r--r-- | Doc/whatsnew/3.3.rst | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/Doc/whatsnew/3.3.rst b/Doc/whatsnew/3.3.rst index 717e4e4..3cd4dd1 100644 --- a/Doc/whatsnew/3.3.rst +++ b/Doc/whatsnew/3.3.rst @@ -55,6 +55,17 @@ PEP XXX: Stub ============= +PEP 393: Flexible String Representation +======================================= + +XXX Add list of changes introduced by :pep:`393` here: + +* The value of :data:`sys.maxunicode` is now always ``1114111`` (``0x10FFFF`` + in hexadecimal). The :c:func:`PyUnicode_GetMax` function still returns + either ``0xFFFF`` or ``0x10FFFF`` for backward compatibility, and it should + not be used with the new Unicode API (see :issue:`13054`). + + Other Language Changes ====================== |