Re: [Python-Dev] Undocumented view==NULL argument in PyObject_GetBuffer()

2012-03-06 Thread Stefan Krah
Nick Coghlan wrote: > On Tue, Mar 6, 2012 at 8:34 PM, Stefan Krah wrote: > > The obvious question is: Will anyone need view==NULL in the future or > > can we remove the special case? > > The public API will still need a guard (to report an error), but +1 > for otherwise eliminating the undocumen

Re: [Python-Dev] Undocumented view==NULL argument in PyObject_GetBuffer()

2012-03-06 Thread Stefan Behnel
Nick Coghlan, 06.03.2012 12:19: > On Tue, Mar 6, 2012 at 8:34 PM, Stefan Krah wrote: >> The obvious question is: Will anyone need view==NULL in the future or >> can we remove the special case? > > The public API will still need a guard (to report an error), but +1 > for otherwise eliminating the u

Re: [Python-Dev] Undocumented view==NULL argument in PyObject_GetBuffer()

2012-03-06 Thread Nick Coghlan
On Tue, Mar 6, 2012 at 8:34 PM, Stefan Krah wrote: > The obvious question is: Will anyone need view==NULL in the future or > can we remove the special case? The public API will still need a guard (to report an error), but +1 for otherwise eliminating the undocumented special case. Cheers, Nick.

[Python-Dev] Undocumented view==NULL argument in PyObject_GetBuffer()

2012-03-06 Thread Stefan Krah
Hello, PyObject_GetBuffer() had an undocumented variant that was used internally: PyObject_GetBuffer(obj, NULL, flags) view==NULL has never been allowed by either PEP-3118 or the documentation: PEP: "The first variable is the "exporting" object. The second argument is the address to