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 ncoghlan
Recipients Arfrever, georg.brandl, loewis, mark.dickinson, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner
Date 2012-08-11.19:16:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344712593.18.0.190830163257.issue13072@psf.upfronthosting.co.za>
In-reply-to
Content
There's still work to be done. The current status in 3.3 trunk is that:

Wide build:
>>> memoryview(array("u")).format
'w'

Narrow build:
>>> memoryview(array("u")).format
'u'

Neither of these are valid struct formats, thus they don't play nicely with the assumptions of memoryview (or any other PEP 3118 consumer). Stefan's memoryview changes are needed because there are *valid* struct formats that memoryview doesn't understand (yet), but it's only coincidental that they will reduce the severity of this problem.

Victor's latest patch switches the 'w' and 'u' for the appropriate integer sizes 'I' and 'H' which I think is an excellent approach.

There are also the post-reversion documentation changes Georg requested to bring the docs back into line with PEP 393
History
Date User Action Args
2012-08-11 19:16:33ncoghlansetrecipients: + ncoghlan, loewis, georg.brandl, mark.dickinson, pitrou, vstinner, Arfrever, skrah, meador.inge, python-dev
2012-08-11 19:16:33ncoghlansetmessageid: <1344712593.18.0.190830163257.issue13072@psf.upfronthosting.co.za>
2012-08-11 19:16:32ncoghlanlinkissue13072 messages
2012-08-11 19:16:32ncoghlancreate