A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] PEP 263 -- Python Source Code Encoding [Python-Dev] PEP 263 -- Python Source Code EncodingM.-A. Lemburg mal@lemburg.com
Wed, 27 Feb 2002 10:48:25 +0100
"Martin v. Loewis" wrote:
> 
> "M.-A. Lemburg" <mal@lemburg.com> writes:
> 
> > 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.
> 
> Do you suggest that in this phase, the declared encoding is not used
> for anything except to complain? 

No. This is just an extra step on top of what is proposed in
the PEP to make people aware of the problem in phase 1.

-- 
Marc-Andre Lemburg
CEO eGenix.com Software GmbH
______________________________________________________________________
Company & Consulting:                           http://www.egenix.com/
Python Software:                   http://www.egenix.com/files/python/



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