The array module is using a different typecode for unicode array
depending on UCS2 or UCS4:

#define Py_UNICODE_SIZE 4

#if Py_UNICODE_SIZE >= 4
#define Py_UNICODE_WIDE
#endif

#ifdef Py_UNICODE_WIDE
#define PyArr_UNI 'w'
#define PyArr_UNISTR "w"
#else
#define PyArr_UNI 'u'
#define PyArr_UNISTR "u"
#endif

It's causing a bunch of unit test to fail which depend on 'u' as the
type code for an unicode array. I don't see the benefit from specifying
an alternative typecode for wide unicode arrays. It may be useful to
have an additional typecode that fails for UCS-2 builds.

My patch keeps 'u' in every build and adds 'w' as an alias for 'u' in
UCS-4 builds only. It also introduces the new module variable typecodes
which is a unicode string containing all valid typecodes.

svn annotate shows that you implemented the 'w' typecode in revision
57181. What do you think about my patch and my proposal?

Can this be closed now that Travis reverted his patch?

This issue may be closed.

> Can this be closed now that Travis reverted his patch?

Yes, it can be closed.

By the way svn.python.org and the anon svn server are down the third
time this week. Something is wrong with the server.

Christian

Oh stop, the array module doesn't build for me (Ubuntu Linux, i386,
UCS-4 build, rev58458):

Modules/arraymodule.c: In function 'array_buffer_getbuf':
Modules/arraymodule.c:1815: error: 'Py_buffer' has no member named 'formats'

Please replace formats with format in line 1815:

    view->format = "w";

Christian

> Oh stop, the array module doesn't build for me (Ubuntu Linux, i386,
> UCS-4 build, rev58458):
>
> Modules/arraymodule.c: In function 'array_buffer_getbuf':
> Modules/arraymodule.c:1815: error: 'Py_buffer' has no member named 'formats'
>
> Please replace formats with format in line 1815:
>
>     view->format = "w";

Done.