RetroSearch Browse

Sun Jul 6 13:17:23 CEST 2008 · http://mail.python.org/pipermail/python-dev/2008-July/080973.html

Le dimanche 06 juillet 2008 à 00:28 +0200, "Martin v. Löwis" a écrit :
> I propose that new codes s*, t*, w* are added, and that s#,t#,w# refuses
> objects which implement a releasebuffer procedure (alternatively, s# etc
> might be removed altogether right away). Users of s* then need to pass
> in a Py_Buffer view pointer that gets filled, and need to explicitly
> release the buffer. For convenience, it might help if the Py_buffer
> structure includes a borrowed PyObject* to the underlying object, along
> with a PyBuffer_Release procedure/macro.

Why a borrowed reference rather than a new one? It could be decref'ed as
part as the proposed PyBuffer_Release procedure.

Overall it sounds like a clean resolution of the problem.

Regards

Antoine.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2008-July/080973.html below:

[Python-Dev] bytearray and array.array are not thread-safe