RetroSearch Browse

Tue May 10 20:48:19 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-May/053610.html

On May 9, 2005, at 12:59 AM, Martin v. Löwis wrote:

>> Wow, what an inane way of looking at it.  I don't know what world you
>> live in, but in my world, users read the configure options and suppose
>> that they mean something.  In fact, they *have* to go off on their own
>> to assume something, because even the documentation you refer to above
>> doesn't say what happens if they choose UCS-2 or UCS-4.  A logical
>> assumption would be that python would use those CEFs internally, and
>> that would be incorrect.
>
> Certainly. That's why the documentation should be improved. Changing
> the option breaks existing packaging systems, and should not be done
> lightly.

I'm perfectly happy to continue supporting --enable-unicode=ucs2, but 
not displaying it as an option.  Is that acceptable to you?

--
Nick

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

Showing content from https://mail.python.org/pipermail/python-dev/2005-May/053610.html below:

[Python-Dev] New Py_UNICODE doc