Supporting chained objects that redirect getbuffer requests to a single
exporter rather than re-exporting the buffer is a matter of removing an
assert, but it needs tests and documentation updates.

New changeset f1441971b621 by Stefan Krah in branch 'default':
Issue #14181: Allow memoryview construction from an object that uses the
http://hg.python.org/cpython/rev/f1441971b621

I didn't ask for review since in the production code only the assert()
line is removed. There are a couple of new tests and I have a private
version of test_buffer that runs most tests with an ndarray chain
using either redirection or re-exporting. As expected, there are no
problems in allowing getbuffer redirection.

Leaving this open as a documentation issue.

New changeset 3a1f7c9f0b25 by Stefan Krah in branch 'default':
Issue #14181: Test creating memoryviews from a static exporter with both
http://hg.python.org/cpython/rev/3a1f7c9f0b25

I'm abusing the issue to settle all concerns that came up on python-dev:

The tests added in the latest commit show that it's indeed no
problem if an atypical static exporter sets view.obj to NULL.

Then I'm abusing this ticket to say: thanks for verifying this.

New changeset 9f7d06a9eabe by Stefan Krah in branch 'default':
Issue #14181: Preserve backwards compatibility for getbufferprocs that a) do
http://hg.python.org/cpython/rev/9f7d06a9eabe

> Then I'm abusing this ticket to say: thanks for verifying this.

I would still like to sweep this fact under the rug. :)


Could you have a look at the documentation patch and see if it's clearer?

Yes, I think this is much clearer.

New changeset da2aaced21bd by Stefan Krah in branch 'default':
Issue #14181: Improve clarity in the documentation for the multi-purpose
http://hg.python.org/cpython/rev/da2aaced21bd

OK, for me the view->obj issues are done. The new tests indicate
that we can silently keep backwards compatibility for view->obj==NULL,
but I suppressed that fact in the documentation because it's already
complicated enough.

Perhaps we might want to deprecate (if one can deprecate an
undocumented feature) view->obj==NULL at some point.



Stefan, thanks for bringing all this up on python-dev!