From: Jeroen Ruigrok van der Werven Date: Sat, 25 Apr 2009 20:44:58 +0000 (+0000) Subject: Issue #4129: int -> Py_ssize_t documentation. X-Git-Tag: v2.7a1~1385 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9594c2c5aa674624af861fdad95cb9eed7f575e1;p=python Issue #4129: int -> Py_ssize_t documentation. --- diff --git a/Doc/c-api/objbuffer.rst b/Doc/c-api/objbuffer.rst index 13ccd6b502..93f5ff0f02 100644 --- a/Doc/c-api/objbuffer.rst +++ b/Doc/c-api/objbuffer.rst @@ -23,6 +23,10 @@ shortcomings of the protocol, and has been backported to Python 2.6. See .. versionadded:: 1.6 + .. versionchanged:: 2.5 + This function used an :ctype:`int *` type for *buffer_len*. This might + require changes in your code for properly supporting 64-bit systems. + .. cfunction:: int PyObject_AsReadBuffer(PyObject *obj, const void **buffer, Py_ssize_t *buffer_len) @@ -34,6 +38,10 @@ shortcomings of the protocol, and has been backported to Python 2.6. See .. versionadded:: 1.6 + .. versionchanged:: 2.5 + This function used an :ctype:`int *` type for *buffer_len*. This might + require changes in your code for properly supporting 64-bit systems. + .. cfunction:: int PyObject_CheckReadBuffer(PyObject *o) @@ -52,3 +60,7 @@ shortcomings of the protocol, and has been backported to Python 2.6. See .. versionadded:: 1.6 + .. versionchanged:: 2.5 + This function used an :ctype:`int *` type for *buffer_len*. This might + require changes in your code for properly supporting 64-bit systems. +