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

Showing content from http://mail.python.org/pipermail/python-dev/2015-November/142178.html below:

[Python-Dev] Support of UTF-16 and UTF-32 source encodings

• Previous message (by thread): [Python-Dev] Support of UTF-16 and UTF-32 source encodings
• Next message (by thread): [Python-Dev] Support of UTF-16 and UTF-32 source encodings
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

"Stephen J. Turnbull" <stephen at xemacs.org> writes:
> I don't see any good reason for allowing non-ASCII-compatible
> encodings in the reference CPython interpreter.

There might be a case for having the tokenizer not care about encodings
at all and just operate on a stream of unicode characters provided by a
different layer.

• Previous message (by thread): [Python-Dev] Support of UTF-16 and UTF-32 source encodings
• Next message (by thread): [Python-Dev] Support of UTF-16 and UTF-32 source encodings
• 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