Message 120318 - Python tracker

➜

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	rupole
Recipients	ncoghlan, pitrou, rupole
Date	2010-11-03.11:59:53
SpamBayes Score	2.2396698e-05
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
While on the subject, the docs for PyMemoryView_FromBuffer state that the resulting memoryview takes ownership of the Py_buffer struct and is responsible for freeing any associated memory. It does not do so, which is not surprising. The absence of a standard for allocation makes it absolutely impossible for it to do so safely.

While on the subject, the docs for PyMemoryView_FromBuffer state that the resulting memoryview takes ownership of the Py_buffer struct and is responsible for freeing any associated memory.  It does not do so, which is not surprising.  The absence of a standard for allocation makes it absolutely impossible for it to do so safely.

History
Date	User	Action	Args
2010-11-03 11:59:54	rupole	set	recipients: + rupole, ncoghlan, pitrou
2010-11-03 11:59:54	rupole	set	messageid: <[email protected]>
2010-11-03 11:59:53	rupole	link	issue10181 messages
2010-11-03 11:59:53	rupole	create