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

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

[Python-Dev] Divorcing str and unicode (no more implicitconversions).

• Previous message: [Python-Dev] Divorcing str and unicode (no more implicitconversions).
• Next message: [Python-Dev] Divorcing str and unicode (no more implicitconversions).
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Fredrik Lundh wrote:
> however, for Python 3000, it would be nice if the source-code encoding applied
> to the *entire* file (XML-style), rather than just unicode string literals and (hope-
> fully) comments and docstrings.

As MAL explains, the encoding currently does apply to the entire file.
However, because of the Python syntax, you are restricted to ASCII
in many places, such as keywords, number literals, and (unfortunately)
identifiers. Lifting the restriction on identifiers is on my agenda.

Regards,
Martin

• Previous message: [Python-Dev] Divorcing str and unicode (no more implicitconversions).
• Next message: [Python-Dev] Divorcing str and unicode (no more implicitconversions).
• 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