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/2001-July/015992.html below:

Defining Unicode Literal Encodings (revision 1.1)

[Python-Dev] Re: PEP: Defining Unicode Literal Encodings (revision 1.1) [Python-Dev] Re: PEP: Defining Unicode Literal Encodings (revision 1.1)Paul Prescod paulp@ActiveState.com
Sun, 15 Jul 2001 10:15:28 -0700
Guido van Rossum wrote:
> 
> Explain again why a directive is better than a specially marked
> comment, when your main goal seems to be to make it easy for
> non-parsing tools like editors to find it?
>...

Parsing tools do need it. The directive changes the file's semantics.
Both parsing and non-parsing tools need it.

I could live with a comment but I think that that is actually harder to
implement so I don't understand the benefit...I'm still trying to
understand what tools we are protecting. compiler.py can be easily
fixed. The real parser/compiler can be easily fixed. The other tools
mostly take their cue from one of these two modules, right?
-- 
Take a recipe. Leave a recipe.  
Python Cookbook!  http://www.ActiveState.com/pythoncookbook



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