Message 93137 - 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	pitrou
Recipients	chuck, exarkun, georg.brandl, gregory.p.smith, ivank, loewis, pitrou
Date	2009-09-25.20:35:32
SpamBayes Score	7.5130433e-06
Marked as misclassified	No
Message-id	<1253911145.5364.178.camel@localhost>
In-reply-to	<1253517719.13.0.582769224456.issue6071@psf.upfronthosting.co.za>

Content
> I tried to implement the new buffer API, but as soon as I add > bf_getbuffer/bf_releasebuffer to PyBufferProcs writing an array to a file > breaks: You should take a look at the array module in py3k, it supports the new buffer API. With a bit of luck, the two relevant functions shouldn't be too difficult to backport to the trunk. By the way, to signal that it supports the new buffer API, you must add Py_TPFLAGS_HAVE_NEWBUFFER to the type flags.

> I tried to implement the new buffer API, but as soon as I add 
> bf_getbuffer/bf_releasebuffer to PyBufferProcs writing an array to a file 
> breaks:

You should take a look at the array module in py3k, it supports the new
buffer API. With a bit of luck, the two relevant functions shouldn't be
too difficult to backport to the trunk.

By the way, to signal that it supports the new buffer API, you must add
Py_TPFLAGS_HAVE_NEWBUFFER to the type flags.

History
Date	User	Action	Args
2009-09-25 20:35:33	pitrou	set	recipients: + pitrou, loewis, georg.brandl, gregory.p.smith, exarkun, ivank, chuck
2009-09-25 20:35:32	pitrou	link	issue6071 messages
2009-09-25 20:35:32	pitrou	create