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 skrah
Recipients Arfrever, georg.brandl, mark.dickinson, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner
Date 2012-08-06.13:19:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Did you see attached patch array_unicode_format.patch? It uses struct
> format "H" or "I" depending on the size of wchar_t.

I totally overlooked that. Given that memoryview can be fixed to
compare buffers with unknown formats, I don't have a strong opinion
on whether array's getbufferproc should alter the format codes of 'u'
and 'w' or not.

The only advantage for memoryview would be that tolist() etc.
would work. However, tolist() previously only worked for bytes,
so in this case raising an exception for 'u' and 'w' is not a
regression but an improvement. :)

If we're deprecating 'u' and 'w' anyway, the getbufferproc should
probably continue to return 'u' and 'w' until the removal of these
format codes.
Date User Action Args
2012-08-06 13:19:34skrahsetrecipients: + skrah, georg.brandl, mark.dickinson, ncoghlan, pitrou, vstinner, Arfrever, meador.inge, python-dev
2012-08-06 13:19:34skrahsetmessageid: <>
2012-08-06 13:19:34skrahlinkissue13072 messages
2012-08-06 13:19:33skrahcreate