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).
diff --git a/Misc/NEWS b/Misc/NEWS
index 6c1fddb..7340607 100644
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -12,6 +12,12 @@
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.