[issue36919] Exception from 'compile' reports a newline char not present in input

Pavel Koneski added the comment: If "equivalent input" is acceptable, then it looks like case B: other implementations possibly having different forms of equivalent input. I am going to post this question on python-dev. -- versions: +Python 3.5,

[issue36919] Exception from 'compile' reports a newline char not present in input

Change by Pavel Koneski : -- versions: -Python 3.5, Python 3.6 ___ Python tracker <https://bugs.python.org/issue36919> ___ ___ Python-bugs-list mailin

[issue36919] Exception from 'compile' reports a newline char not present in input

Pavel Koneski added the comment: > I'm assuming the real issue is wanting to make IronPython pass as much of the > CPython test suite as possible. This is indeed the case. The CPython test suite is invaluable in guiding IronPython development. Most of the time, the tests are pre

[issue36919] Exception from 'compile' reports a newline char not present in input

Change by Pavel Koneski : -- keywords: +patch pull_requests: +13535 stage: -> patch review pull_request: https://github.com/python/cpython/pull/13639 ___ Python tracker <https://bugs.python.org/issu

[issue36919] Exception form 'compile' reports a newline char not present in input

New submission from Pavel Koneski : Since Python 3.2, input in 'exec' mode of 'compile' does not have to end in a newline anymore. However, it creates a surprising behavior when a 'SyntaxError' is reported: >>> try: compile('try', '