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, kristjan.jonsson, loewis, mark.dickinson, ncoghlan, paul.moore, petri.lehtinen, pitrou, pv, python-dev, rupole, skrah, teoliphant, vstinner
Date 2012-03-02.13:14:40
SpamBayes Score 0.0034132225
Marked as misclassified No
Message-id <1330694081.17.0.322828562236.issue10181@psf.upfronthosting.co.za>
In-reply-to
Content
It occurs to me that one thing that *could* be backported to early versions are some of the documentation improvements on how to correctly handle the lifecycle of fields in Py_buffer. That gets messy though because memoryview doesn't behave nicely in those versions, so we'd be violating our own guidelines.

Perhaps the relevant sections should be updated with a reference saying that the semantics have been cleaned up in 3.3, and if in doubt, try to follow the 3.3 documentation?
History
Date User Action Args
2012-03-02 13:14:41ncoghlansetrecipients: + ncoghlan, loewis, teoliphant, paul.moore, mark.dickinson, rupole, pitrou, kristjan.jonsson, vstinner, pv, skrah, python-dev, jcon, petri.lehtinen
2012-03-02 13:14:41ncoghlansetmessageid: <1330694081.17.0.322828562236.issue10181@psf.upfronthosting.co.za>
2012-03-02 13:14:40ncoghlanlinkissue10181 messages
2012-03-02 13:14:40ncoghlancreate