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

Showing content from https://mail.python.org/pipermail/python-dev/2015-November/142174.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] [Python-checkins] Daily reference leaks (97e2a6810f7f): sum=10
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sat, Nov 14, 2015 at 09:19:37PM +0200, Serhiy Storchaka wrote:

> If the support of UTF-16 and UTF-32 is planned, I'll take this to 
> attention during refactoring. But in many places besides the tokenizer 
> the ASCII compatible encoding of source files is expected.

Perhaps another way of looking at this:

Is it feasible to drop support for arbitrary encodings and just require 
UTF-8 (with or without a pseudo-BOM)?



-- 
Steve

• Previous message (by thread): [Python-Dev] Support of UTF-16 and UTF-32 source encodings
• Next message (by thread): [Python-Dev] [Python-checkins] Daily reference leaks (97e2a6810f7f): sum=10
• 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