[ python-Feature Requests-1144057 ] future warning in commets

[SourceForge.net]

Feature Requests item #1144057, was opened at 2005-02-18 16:10
Message generated for change (Comment added) made by mcherm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1144057&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Parser/Compiler
Group: None
>Status: Closed
Resolution: Rejected
Priority: 5
Submitted By: Grzegorz Makarewicz (makaron)
Assigned to: M.-A. Lemburg (lemburg)
Summary: future warning in commets

Initial Comment:
Python uses '#' as start of comment, generally these
lines can (should) be ignored by python compiler but ..
deprecation warnings are issued when comment contains
non ascii letters - ord(ch) not in range 0-127

can we disable it in this situation ?

----------------------------------------------------------------------

>Comment By: Michael Chermside (mcherm)
Date: 2005-12-28 11:41

Message:
Logged In: YES 
user_id=99874

Rejecting, as per lemburg.

----------------------------------------------------------------------

Comment By: M.-A. Lemburg (lemburg)
Date: 2005-02-23 08:44

Message:
Logged In: YES 
user_id=38388

+1, this request is not in line with the source code
encoding PEP.
Rejecting the request.


----------------------------------------------------------------------

Comment By: Michael Chermside (mcherm)
Date: 2005-02-23 08:33

Message:
Logged In: YES 
user_id=99874

I agree with doerwalter. If the file is in ascii, then it
should be in ascii... even comments. If it's not in ascii,
that's fine, but it needs to be marked as to what encoding
it IS in. I don't happen to know of any encodings in which
certain bytes with the high bit set indicate newlines, but
imagine that there were one. The newline marks the end of
the comment, so it makes a syntactic difference in the
program... we must be able to recognize newlines in order to
parse the file. And if we don't know the encoding, then how
can we possibly recognize newlines?

I propose rejecting the patch.

----------------------------------------------------------------------

Comment By: Walter Dörwald (doerwalter)
Date: 2005-02-21 04:17

Message:
Logged In: YES 
user_id=89016

I don't think we should change this. The encoding is
something that affects the whole file not just the
executable part of it. When a file that claims to be ASCII
contains bytes > 0x7f there's something fishy going on, no
matter where these bytes are.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1144057&group_id=5470