Message 144658 - 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	vstinner
Recipients	pitrou, vstinner
Date	2011-09-30.00:09:49
SpamBayes Score	2.692945e-05
Marked as misclassified	No
Message-id	<1317341390.65.0.255779328054.issue13072@psf.upfronthosting.co.za>
In-reply-to

Content
In Python 3.2, when you get a buffer from array.array('u'), "u" is used as buffer format. The format is supposed to be a format from the struct module, and "u" is an invalid struct format. "w" is used on wide mode. I just upgraded the array module to use the new Unicode API (PEP 393). The array now uses a Py_UCS4 buffer. I used "I" or "L" format depending on the size of int and long C types. It would be better to use a format for a Py_UCS4 string, but struct doesn't support such type. For Python 2.7 and 3.2, I don't know if it is really a bug or not.

In Python 3.2, when you get a buffer from array.array('u'), "u" is used as buffer format. The format is supposed to be a format from the struct module, and "u" is an invalid struct format. "w" is used on wide mode.

I just upgraded the array module to use the new Unicode API (PEP 393). The array now uses a Py_UCS4 buffer. I used "I" or "L" format depending on the size of int and long C types.

It would be better to use a format for a Py_UCS4 string, but struct doesn't support such type.

For Python 2.7 and 3.2, I don't know if it is really a bug or not.

History
Date	User	Action	Args
2011-09-30 00:09:50	vstinner	set	recipients: + vstinner, pitrou
2011-09-30 00:09:50	vstinner	set	messageid: <1317341390.65.0.255779328054.issue13072@psf.upfronthosting.co.za>
2011-09-30 00:09:50	vstinner	link	issue13072 messages
2011-09-30 00:09:49	vstinner	create