RetroSearch Browse

Fri Mar 22 05:11:20 EDT 2019 · https://mail.python.org/pipermail/python-dev/2019-March/156814.html

On Fri, Mar 22, 2019 at 4:38 PM Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
>
> A poster on comp.lang.python is asking about array.array('u').
> He wants an efficient mutable collection of unicode characters
> that can be initialised from a string.
>
> According to the docs, the 'u' code is deprecated and will be
> removed in 4.0, but no alternative is suggested.
>
> Why is this being deprecated, instead of keeping it and making
> it always 32 bits? It seems like useful functionality that can't
> be easily obtained another way.
>

I think it's because there are not much use cases found
when implementing PEP 393.

If there are use cases enough to keep it in stdlib, I'm OK
about un-deprecate it and make it always 32bit (int32_t).

-- 
Inada Naoki  <songofacandy at gmail.com>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2019-March/156814.html below:

[Python-Dev] Replacement for array.array('u')?