This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients georg.brandl, loewis, pitrou, teoliphant
Date 2008-08-15.20:19:48
SpamBayes Score 0.0050814473
Marked as misclassified No
Message-id <1218831594.01.0.816841363166.issue3560@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, here is a simple patch. It:
- moves the struct definition at the end of memoryobject.h with a
comment that the definition should not be considered public
- adds two macros for accessing the underlying Py_buffer* and PyObject*,
respectively
- removes the ill-named PyMemoryView() macro (PyMemoryView_GET_BUFFER()
can be used instead)
- renames PyMemory_Check() to PyMemoryView_Check()
- renames PyMemoryView_FromMemory() to PyMemoryView_FromBuffer()

I didn't try to clean up the existing documentation comments, although I
find them difficult to follow. I also didn't change anything in the
semantics and implementation of the memoryview object.

Let me know what you think.
History
Date User Action Args
2008-08-15 20:19:54pitrousetrecipients: + pitrou, loewis, georg.brandl, teoliphant
2008-08-15 20:19:54pitrousetmessageid: <1218831594.01.0.816841363166.issue3560@psf.upfronthosting.co.za>
2008-08-15 20:19:52pitroulinkissue3560 messages
2008-08-15 20:19:51pitroucreate