[Python-3000] Single buffer implied in new buffer protocol?

[Greg Ewing]

Stefan Behnel wrote:
> So that means it's fine to remove all locking related functionality from the
> new buffer protocol and leave everything to application space, right?

Not quite all of it -- the buffer needs to be considered
as locked against moving between calls to getbuffer and
releasebuffer, and providers that can move their memory
need to keep a count of outstanding getbuffer calls.

All the locking-related flags can go, though, since
there is only one kind of lock and it's implied by the
getbuffer call itself.

-- 
Greg