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 ncoghlan
Recipients gvanrossum, ncoghlan, pitrou
Date 2010-09-07.22:03:42
SpamBayes Score 3.0938731e-06
Marked as misclassified No
Message-id <>
In-reply-to <1283874980.3234.4.camel@localhost.localdomain>
>> Is this not covered by PEP 3118 at all?
> The PEP says “this memory view object holds on to the memory of base
> [i.e. the object the buffer was acquired from] until it is deleted”.
> Apparently issues pertaining to delayed garbage collection weren't
> raised at the time.

As with a few(!) other things in relation to this PEP, the primary
consumers were most interested in the C API side of things, so we
collectively missed relevant details on the Python side.

+1 on adding release() (obviously), and +1 on direct support for
context management (it seems very analogous to file.close to me, so
direct support makes more sense than leaving it out).
Date User Action Args
2010-09-07 22:03:45ncoghlansetrecipients: + ncoghlan, gvanrossum, pitrou
2010-09-07 22:03:43ncoghlanlinkissue9757 messages
2010-09-07 22:03:43ncoghlancreate