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 pitrou, teoliphant
Date 2008-08-15.09:37:01
SpamBayes Score 1.74476e-05
Marked as misclassified No
Message-id <1218793027.62.0.312203864665.issue3560@psf.upfronthosting.co.za>
In-reply-to
Content
PyMemoryViewObject has a "base" field which points to the originator of
the buffer. However, this field has become redundant now that the
Py_buffer struct has received an "obj" field which also points to the
originator of the buffer (this has been done as part of the fix to #3139).

Not removing "base" would make for a confusing and error-prone API.
However, removing it is complicated by the fact that "base" is sometimes
abused to contain a tuple (for PyBUF_SHADOW type buffers, which are
neither mentioned in the PEP nor used anywhere in py3k).
History
Date User Action Args
2008-08-15 09:37:08pitrousetrecipients: + pitrou, teoliphant
2008-08-15 09:37:07pitrousetmessageid: <1218793027.62.0.312203864665.issue3560@psf.upfronthosting.co.za>
2008-08-15 09:37:05pitroulinkissue3560 messages
2008-08-15 09:37:02pitroucreate