[Python-bugs-list] [ python-Bugs-780730 ] PEP-263 and 278

[SourceForge.net]

Bugs item #780730, was opened at 2003-07-31 11:16
Message generated for change (Comment added) made by loewis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=780730&group_id=5470

Category: Parser/Compiler
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: atsuo ishimoto (ishimoto)
Assigned to: Nobody/Anonymous (nobody)
Summary: PEP-263 and 278

Initial Comment:
Universal Newline Support doesn't work for source files
that contain encoding definition.


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

>Comment By: Martin v. Löwis (loewis)
Date: 2003-08-01 10:22

Message:
Logged In: YES 
user_id=21627

I see. This is not about PEP 278, though, as you are not
calling any open() function, and passing no 'U' argument to
it - cross-platform newlines should work independent of that
PEP.

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

Comment By: atsuo ishimoto (ishimoto)
Date: 2003-08-01 09:35

Message:
Logged In: YES 
user_id=463672

Attached file has encoding definition and it's newline is '\r'.
Executing this script on Windows 2000, I got following error.
But it runs fine if I remove encoding definition. 

C:\Python23>python .\test.py
  File ".\test.py", line 2
a() print 'hi'
            ^
SyntaxError: invalid syntax


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

Comment By: Martin v. Löwis (loewis)
Date: 2003-08-01 09:04

Message:
Logged In: YES 
user_id=21627

It's not clear to me what the problem is: Source code files
and universal newline support have nothing to do with each
other.

Can you attach a small example that demonstrates the problem?

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

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