➜

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 skrah
Recipients Alexander.Belopolsky, belopolsky, docs@python, ncoghlan, pitrou, skrah
Date 2012-08-31.19:12:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20120831191212.GA2642@sleipnir.bytereef.org>
In-reply-to <CAP7h-xbddU2uc=UEL=TGTeY3dBJf+kfV1qS=8PYGohikWY5y8A@mail.gmail.com>
Content 
Alexander Belopolsky <report@bugs.python.org> wrote:
> I am still getting up to speed with all the changes that went in since
> 3.2.  I'll review your patch over the weekend.  Meanwhile, I think the
> goal should be that after PyMemoryview_FromBuffer(info) is called, it
> should be OK to discard info by calling PyBuffer_Release()

Now I'm puzzled: I thought your goal was to preserve the implicit cleanup
from 3.2, i.e. PyBuffer_Release() is called when the managed buffer is
deallocated.

Without the patch it's OK to call PyBuffer_Release(info) after
PyMemoryview_FromBuffer(info). With the patch you can't call
PyBuffer_Release(info), since it's done automatically already.
History
Date User Action Args
2012-08-31 19:12:12skrahsetrecipients: + skrah, ncoghlan, belopolsky, pitrou, Alexander.Belopolsky, docs@python
2012-08-31 19:12:11skrahlinkissue15821 messages
2012-08-31 19:12:11skrahcreate