[issue14811] compile fails - UTF-8 character decoding

Serhiy Storchaka added the comment: Function decoding_fgets (Parser/tokenizer.c) reads line in buffer of fixed size 8192 (line truncated to size 8191) and then fails because line is cut in the middle of a multibyte UTF-8 character. -- ___ Python tr

[issue14811] compile fails - UTF-8 character decoding

Serhiy Storchaka added the comment: And for Python 2.7 too. -- versions: +Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mail

[issue14811] compile fails - UTF-8 character decoding

Serhiy Storchaka added the comment: I can reproduce it on Linux. Minimal example: $ ./python -c "open('longline.py', 'w').write('#' + repr('\u00A1' * 4096) + '\n')" $ ./python longline.py File "longline.py", line 1 SyntaxError: Non-UTF-8 code starting with '\xc2' in file longline.py on line

[issue14811] compile fails - UTF-8 character decoding

Antoine Pitrou added the comment: I tried to reproduce but failed to compile a Windows Python - see issue14813. -- components: +Windows nosy: +pitrou versions: +Python 3.3 ___ Python tracker __

[issue14811] compile fails - UTF-8 character decoding

Hynek Schlawack added the comment: You are right, file system encoding was platform dependent, not file encoding. This space-after-parentheses trigger is odd; I'm adding the Windows guys to the ticket. Please tell us also your exact version of Windows. -- components: -Interpreter Cor

[issue14811] compile fails - UTF-8 character decoding

Glenn Linderman added the comment: There is no traceback. Here is the text of the Syntax error. d:\my\im\infiles>c:\python32\python.exe d:\my\py\t33a.py -h File "d:\my\py\t33a.py", line 2 SyntaxError: Non-UTF-8 code starting with '\xc3' in file d:\my\py\t33a.py on line 3, but no encoding de

[issue14811] compile fails - UTF-8 character decoding

Hynek Schlawack added the comment: Would you mind adding more information like the full traceback? By saying "compilation error", I presume you mean the compilation of the t33a.py file into byte code (and not compilation of Python itself)? I can't reproduce it neither with the vanilla 3.2.3 o

[issue14811] compile fails - UTF-8 character decoding

Changes by Ezio Melotti : -- components: +Unicode nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue14811] compile fails - UTF-8 character decoding

Glenn Linderman added the comment: Forgot to mention that I was running on Windows, 64-bit. -- ___ Python tracker ___ ___ Python-bugs

[issue14811] compile fails - UTF-8 character decoding

New submission from Glenn Linderman : t33a.py demonstrates a compilation problem. OK, it has a long line, but making it one space longer (add a space after the left parenthesis) makes it work... so it must not be line length alone. Rather, since the error is about a bad UTF-8 character start