[issue15035] array.array of UCS2 values

Change by Inada Naoki : -- nosy: +inada.naoki ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15035] array.array of UCS2 values

Changes by Christian Heimes li...@cheimes.de: -- nosy: +christian.heimes versions: +Python 3.4 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15035 ___

[issue15035] array.array of UCS2 values

Stefan Krah added the comment: This one should be fixed by #13072. Could you check again? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15035 ___

[issue15035] array.array of UCS2 values

Nick Coghlan added the comment: As Stefan noted, so long as Py_UNICODE is 16 bits in the Mac OS X builds, then this should now be back to the 3.2 behaviour. -- nosy: +ncoghlan priority: low - high ___ Python tracker rep...@bugs.python.org

[issue15035] array.array of UCS2 values

Martin v. Löwis added the comment: It's not back to the 3.2 behavior. In 3.3, Py_UNICODE is always equal to wchar_t, which is a 4-byte type on Darwin. However, CFString is based on UniChar, which is a 2-byte type. That this worked in 3.2 was by accident - it would work only in narrow builds.

[issue15035] array.array of UCS2 values

Ronald Oussoren added the comment: Py_UNICODE is an typedef for wchar_t and that type is 4 bytes long: a.tobytes() b'h\x00\x00\x00e\x00\x00\x00l\x00\x00\x00l\x00\x00\x00o\x00\x00\x00 \x00\x00\x00w\x00\x00\x00o\x00\x00\x00r\x00\x00\x00l\x00\x00\x00d\x00\x00\x00' a = array.array('u', 'bar')

[issue15035] array.array of UCS2 values

Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15035 ___

[issue15035] array.array of UCS2 values

New submission from Ronald Oussoren ronaldousso...@mac.com: I'm sometimes using an array.array with format character u as a writable backing store for buffers shared with platform APIs that access buffers of UCS2 values. This works fine in python 3.2 and earlier with a ucs2 build of python,

[issue15035] array.array of UCS2 values

Stefan Krah stefan-use...@bytereef.org added the comment: See also #13072 and the discussion starting at: http://mail.python.org/pipermail/python-dev/2012-March/117390.html I think the priority should be high, since the current behavior doesn't preserve the status quo. Also, PEP-3118 suggests

[issue15035] array.array of UCS2 values

Stefan Krah stefan-use...@bytereef.org added the comment: Hmm, obviously the discussion starts here: http://mail.python.org/pipermail/python-dev/2012-March/117376.html -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15035