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

Showing content from https://mail.python.org/pipermail/python-dev/2002-February/020445.html below:

[Python-Dev] PEP 263 -- Python Source Code Encoding

• Previous message: Japanese codecs (was Re: [Python-Dev] PEP 263 -- Python Source Code Encoding)
• Next message: [Python-Dev] PEP 263 -- Python Source Code Encoding
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wednesday, February 27, 2002, at 10:16 , M.-A. Lemburg wrote:
> In phase 1, the tokenizer checks the *complete file* for
> non-ASCII characters and outputs single warning
> per file if it doesn't find a coding declaration at
> the top. Unicode literals continue to use [raw-]unicode-escape
> as codec.
>
> In phase 2, we enforce ASCII as default encoding, i.e.
> the warning will turn into an error. The [raw-]unicode-escape
> codec will be extended to also support converting Unicode
> to Unicode, that is, only handle escape sequences in this
> case.

+1
--
- Jack Jansen        <Jack.Jansen@oratrix.com>        
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- Emma 
Goldman -

• Previous message: Japanese codecs (was Re: [Python-Dev] PEP 263 -- Python Source Code Encoding)
• Next message: [Python-Dev] PEP 263 -- Python Source Code Encoding
• 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