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

Showing content from https://mail.python.org/pipermail/python-dev/2015-November/142186.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 ]

> On Nov 15, 2015, at 9:34 AM, Guido van Rossum <guido at python.org> wrote:
> 
> Let me just unilaterally end this discussion. It's fine to disregard
> the future possibility of using UTF-16 or -32 for Python source code.
> Serhiy can happily rip out any comments or dead code dealing with that
> possibility.

Thank you.


Raymond

• 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