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 ncoghlan, pitrou, rupole
Date 2010-11-02.22:57:06
SpamBayes Score 4.7885358e-05
Marked as misclassified No
Message-id <1288738629.35.0.53407341178.issue10181@psf.upfronthosting.co.za>
In-reply-to
Content
Read the "Releasing the buffer" section in PEP 3118 again. Unless I'm misunderstanding you completely, the rules you're asking for are already in place: those fields are entirely the responsibility of the exporting object, and it needs to ensure they remain valid until the buffer is released.

Now, it may be that we haven't *implemented* this correctly or consistently in the builtin objects, in which case we should do something about it. But the rules are there.
History
Date User Action Args
2010-11-02 22:57:09ncoghlansetrecipients: + ncoghlan, rupole, pitrou
2010-11-02 22:57:09ncoghlansetmessageid: <1288738629.35.0.53407341178.issue10181@psf.upfronthosting.co.za>
2010-11-02 22:57:06ncoghlanlinkissue10181 messages
2010-11-02 22:57:06ncoghlancreate