summaryrefslogtreecommitdiffstats
path: root/Objects/memoryobject.c
diff options
context:
space:
mode:
authorR David Murray <rdmurray@bitdance.com>2014-10-05 15:47:01 (GMT)
committerR David Murray <rdmurray@bitdance.com>2014-10-05 15:47:01 (GMT)
commit861470c83607a4312d3c65bce3e18414b965e586 (patch)
tree48088d67e50d8599b00498c17b5c8b7a35b482f8 /Objects/memoryobject.c
parentd577cea8ab0d929c40de93947dd68b9709607b35 (diff)
downloadcpython-861470c83607a4312d3c65bce3e18414b965e586.zip
cpython-861470c83607a4312d3c65bce3e18414b965e586.tar.gz
cpython-861470c83607a4312d3c65bce3e18414b965e586.tar.bz2
#16518: Bring error messages in harmony with docs ("bytes-like object")
Some time ago we changed the docs to consistently use the term 'bytes-like object' in all the contexts where bytes, bytearray, memoryview, etc are used. This patch (by Ezio Melotti) completes that work by changing the error messages that previously reported that certain types did "not support the buffer interface" to instead say that a bytes-like object is required. (The glossary entry for bytes-like object references the discussion of the buffer protocol in the docs.)
Diffstat (limited to 'Objects/memoryobject.c')
-rw-r--r--Objects/memoryobject.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/Objects/memoryobject.c b/Objects/memoryobject.c
index 5148ce6..935da04 100644
--- a/Objects/memoryobject.c
+++ b/Objects/memoryobject.c
@@ -792,7 +792,7 @@ PyMemoryView_FromObject(PyObject *v)
}
PyErr_Format(PyExc_TypeError,
- "memoryview: %.200s object does not have the buffer interface",
+ "memoryview: a bytes-like object is required, not '%.200s'",
Py_TYPE(v)->tp_name);
return NULL;
}