Message 139868 - 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	ncoghlan
Recipients	jcon, kermode, mark.dickinson, ncoghlan, petri.lehtinen, pitrou, pv, rupole, skrah, teoliphant, vstinner
Date	2011-07-05.12:59:01
SpamBayes Score	0.0008346928
Marked as misclassified	No
Message-id	<1309870742.28.0.515124876634.issue10181@psf.upfronthosting.co.za>
In-reply-to

Content
To address the "should PyManagedBuffer be public?" question: yes, I think so. Given the amount of grief the raw PEP 3118 API has caused the memoryview implementation, I expect the easier lifecycle management provided by the PyObject based API may also help 3rd parties.

To address the "should PyManagedBuffer be public?" question: yes, I think so.

Given the amount of grief the raw PEP 3118 API has caused the memoryview implementation, I expect the easier lifecycle management provided by the PyObject based API may also help 3rd parties.

History
Date	User	Action	Args
2011-07-05 12:59:02	ncoghlan	set	recipients: + ncoghlan, teoliphant, mark.dickinson, rupole, kermode, pitrou, vstinner, pv, skrah, jcon, petri.lehtinen
2011-07-05 12:59:02	ncoghlan	set	messageid: <1309870742.28.0.515124876634.issue10181@psf.upfronthosting.co.za>
2011-07-05 12:59:01	ncoghlan	link	issue10181 messages
2011-07-05 12:59:01	ncoghlan	create