diff options
| author | Victor Stinner <victor.stinner@haypocalc.com> | 2010-06-08 22:54:19 (GMT) |
|---|---|---|
| committer | Victor Stinner <victor.stinner@haypocalc.com> | 2010-06-08 22:54:19 (GMT) |
| commit | 3dcb5acdb0151d1686762329ec07ae2ac4d1caae (patch) | |
| tree | 1b9d0230afafafa0cff920c7f55c9ca98e433719 /Misc/NEWS | |
| parent | 1fbd36b51d1bf65bc110e51840bede646b58f2d5 (diff) | |
| download | cpython-3dcb5acdb0151d1686762329ec07ae2ac4d1caae.zip cpython-3dcb5acdb0151d1686762329ec07ae2ac4d1caae.tar.gz cpython-3dcb5acdb0151d1686762329ec07ae2ac4d1caae.tar.bz2 | |
Issue #8838, #8339: Remove codecs.charbuffer_encode() and "t#" parsing format
Remove last references to the "char buffer" of the buffer protocol from
Python3.
Diffstat (limited to 'Misc/NEWS')
| -rw-r--r-- | Misc/NEWS | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -12,6 +12,13 @@ What's New in Python 3.2 Alpha 1? Core and Builtins ----------------- +- Issue #8838: Remove codecs.charbuffer_encode() function. The buffer protocol + doesn't support "char buffer" anymore in Python3. + +- Issue #8339: Remove "t#" format of PyArg_Parse*() functions, use "s#" or "s*" + instead. codecs.charbuffer_encode() now accepts modifiable buffer objects + like bytearray. + - Issue #8837: Remove "O?" format of PyArg_Parse*() functions. The format is no used anymore and it was never documented. |