Message 171008 - 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	serhiy.storchaka
Recipients	Arfrever, ezio.melotti, pitrou, serhiy.storchaka, skrah
Date	2012-09-22.17:08:59
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<201209222008.45883.storchaka@gmail.com>
In-reply-to	<1348309826.3392.1.camel@localhost.localdomain>

Content
> I think you should keep the > Py_buffers alive in an array, and only release them at the end (it may > also be slightly faster to do so). However allocation of this array may considerably slow down the function. We may need the special-case for bytes and bytearray. Stop, and the bytearray (or bytearray subclass) can change size between two calls to Py_SIZE()?

> I think you should keep the
> Py_buffers alive in an array, and only release them at the end (it may
> also be slightly faster to do so).

However allocation of this array may considerably slow down the function. We 
may need the special-case for bytes and bytearray. Stop, and the bytearray (or 
bytearray subclass) can change size between two calls to Py_SIZE()?

History
Date	User	Action	Args
2012-09-22 17:08:59	serhiy.storchaka	set	recipients: + serhiy.storchaka, pitrou, ezio.melotti, Arfrever, skrah
2012-09-22 17:08:59	serhiy.storchaka	link	issue15958 messages
2012-09-22 17:08:59	serhiy.storchaka	create