➜

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 Alexander.Belopolsky
Recipients Alexander.Belopolsky, belopolsky, docs@python, ncoghlan, pitrou, skrah
Date 2012-08-31.18:53:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7h-xbddU2uc=UEL=TGTeY3dBJf+kfV1qS=8PYGohikWY5y8A@mail.gmail.com>
In-reply-to <1346438083.63.0.144847991141.issue15821@psf.upfronthosting.co.za>
Content 
On Fri, Aug 31, 2012 at 2:34 PM, Stefan Krah <report@bugs.python.org> wrote:
> With the ManagedBuffer, we could now write a new function that returns
> a memoryview with much nicer cleanup facilities. But that doesn't help
> here since we're stuck with this function for 3.3.0.
>
>
> What do you think? Should this go into 3.3.0?

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() and if info
is not allocated on the stack, Py_DECREF(info).  I think we are almost
there achieving that goal with possible exception of dynamically or
stack-allocated fmt strings.
History
Date User Action Args
2012-08-31 18:54:19Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, ncoghlan, belopolsky, pitrou, skrah, docs@python
2012-08-31 18:53:58Alexander.Belopolskylinkissue15821 messages
2012-08-31 18:53:57Alexander.Belopolskycreate