[issue15625] Support u and w codes in memoryview

[Martin v. Löwis]

Martin v. Löwis added the comment:

> My current inclination is still to apply Victor's patch from #13072  
> (which changes array to export the appropriate integer typecodes for  
> 'u' arrays) and otherwise punt on this for 3.3 and try to sort out  
> the mess for 3.4.

I think this would be the worst choice. It would mean that we change
the format for exported array.arrays now for 3.3, and then change it
in 3.4 again. So anybody who cares about this would have to deal
with three different behaviors.

Note that the array module had been using 'u' and 'w' essentially
"forever" (i.e. since 3.0).

> For 3.4, I'm inclined to favour Stefan's proposal of C, U, W mapping  
> to multi-point sequences of UCS-1, UCS-2, UCS-4 code points (with  
> corresponding typecodes in the array module).

Fine with me in principle, although I see a problem when NumPy uses
'U' for UCS-4, yet CPython declares it to be UCS-2. I also think that
Travis' explicit agreement must be sought.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15625>
_______________________________________