[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)
Mark Dickinson
report at bugs.python.org
Fri Jan 7 10:10:25 CET 2011
Mark Dickinson <dickinsm at gmail.com> added the comment:
> an internal data structure keyed off
> the Py_buffer address.
If we're using the Py_buffer address coming into getbuffer as a key, then we probably shouldn't be using a stack address, since it would be difficult to guarantee uniqueness that way.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10181>
_______________________________________
More information about the Python-bugs-list
mailing list