[issue3046] Locking should be removed from the new buffer protocol

[Travis Oliphant]

Travis Oliphant <oliphant at enthought.com> added the comment:

Greg Ewing's comment in the thread that read/write locking is orthogonal
to memory-buffer moving is to me the most convincing argument that the
locking portion of the getbuffer function call should be removed and
potentially placed in a separate API at some point.   This will simplify
the protocol a bit.  

I will apply the patch.

----------
nosy: +teoliphant

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue3046>
_______________________________________