[issue10293] PyMemoryView object has obsolete members

Stefan Krah added the comment: I think PyBUF_SHADOW was the renamed version of PyBUF_UPDATEIFCOPY from the PEP. :) -- nosy: +skrah ___ Python tracker ___ ___

[issue10293] PyMemoryView object has obsolete members

Kristján Valur Jónsson added the comment: Ah, the SHADOW member... Weird. Anyway, I have been hacking around in the memory view. One thing that it does, and makes me uncomfortable since I think it is breaking the new buffer protocol, is to a) PyObject_GetBuffer() b) Modify the resulting loca

[issue10293] PyMemoryView object has obsolete members

Antoine Pitrou added the comment: Done in r86174. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-b

[issue10293] PyMemoryView object has obsolete members

Antoine Pitrou added the comment: Well, there's this strange-looking thing in PyMemoryView_GetContiguous: if (buffertype == PyBUF_SHADOW) { /* return a shadowed memory-view object */ view->buf = dest; mem->base = PyTuple_Pack(2, obj, bytes); ... but I don't really w

[issue10293] PyMemoryView object has obsolete members

Changes by Georg Brandl : -- assignee: -> pitrou nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10293] PyMemoryView object has obsolete members

New submission from Kristján Valur Jónsson : The PyMemoryObject has a "base" member which appears to be obsolete. Furthermore, the function do_release() attempt to perform some obsolete-looking woodo with base if it happens to be a tuple. Looks dangerous. -- components: Interpreter C