New submission from Terry J. Reedy <tjre...@udel.edu>:
In python-list thread "Does Python 3.1 accept \r\n in compile()?"
jmfauth notes that
compile('print(999)\r\n', '<in>', 'exec')
works in 2.7 but not 3.1 (and 3.2 not checked) because 3.1 sees '\r' as
SyntaxError.
I started to respond that this is part of Py3 cleanup with newlines converted
on input and back-compatibility with ancient Python not needed. Then I saw in
3.2 manual
"Changed in version 3.2: Allowed use of Windows and Mac newlines. ..."
However, above gives same error. Should "Allowed use of Windows and Mac
newlines." be deleted? What else could it mean other than use of '\r' or '\r\n'?
The note was added in r76232 which is a forward port of r76230
"fix several compile() issues by translating newlines in the tokenizer"
by B. Peterson. Is Windows/Mac part just not applicable to 3.2?
----------
assignee: benjamin.peterson
components: Documentation
messages: 124872
nosy: benjamin.peterson, terry.reedy
priority: normal
severity: normal
status: open
title: Compile() and 'Windows/Mac newlines'
versions: Python 3.2
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue10792>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
