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

Showing content from https://mail.python.org/pipermail/python-dev/2004-June/045574.html below:

[Python-Dev] Allowing u.encode() to return non-strings

• Previous message: [Python-Dev] Allowing u.encode() to return non-strings
• Next message: [Python-Dev] Allowing u.encode() to return non-strings
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

M.-A. Lemburg wrote:
>> -1. I find it unfortunate that there are encodings which
>> don't convert between Unicode and byte strings; this direction
>> should not be followed.
>>
>> Instead, text processing utilities should be proper libraries.
> 
> 
> I don't understand... codecs are not limited to only text
> processing. It's a completely independent framework from the
> Unicode sub-system.

I know this is viewed, and perhaps even documented, as a
framework independent of Unicode. I think this is a mistake,
and it should have been constrained to character encodings
(i.e. conversions to and from Unicode, using character tables
or similar algorithms) right from the beginning.

Regards,
Martin

• Previous message: [Python-Dev] Allowing u.encode() to return non-strings
• Next message: [Python-Dev] Allowing u.encode() to return non-strings
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4