diff options
author | Brett Cannon <bcannon@gmail.com> | 2006-06-08 17:00:45 (GMT) |
---|---|---|
committer | Brett Cannon <bcannon@gmail.com> | 2006-06-08 17:00:45 (GMT) |
commit | de3b0522160df86b45075708cd42a0e7d62a9b71 (patch) | |
tree | d7060f822e992ef943d421deb0b52cb5b8b85df0 /Misc | |
parent | 6ee7d01c059f799c0f52ffe94811507bccc688a2 (diff) | |
download | cpython-de3b0522160df86b45075708cd42a0e7d62a9b71.zip cpython-de3b0522160df86b45075708cd42a0e7d62a9b71.tar.gz cpython-de3b0522160df86b45075708cd42a0e7d62a9b71.tar.bz2 |
Buffer objects would return the read or write buffer for a wrapped object when
the char buffer was requested. Now it actually returns the char buffer if
available or raises a TypeError if it isn't (as is raised for the other buffer
types if they are not present but requested).
Not a backport candidate since it does change semantics of the buffer object
(although it could be argued this is enough of a bug to bother backporting).
Diffstat (limited to 'Misc')
-rw-r--r-- | Misc/NEWS | 6 |
1 files changed, 6 insertions, 0 deletions
@@ -12,6 +12,12 @@ What's New in Python 2.5 beta 1? Core and builtins ----------------- +- Buffer objects, at the C level, never used the char buffer + implementation even when the char buffer for the wrapped object was + explicitly requested (originally returned the read or write buffer). + Now a TypeError is raised if the char buffer is not present but is + requested. + - Patch #1346214: Statements like "if 0: suite" are now again optimized away like they were in Python 2.4. |