[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

miss-islington added the comment: New changeset e3ce3bba9277a7c4cfde5aaf6269b6c68f334176 by Miss Islington (bot) in branch '3.9': bpo-40847: Consider a line with only a LINECONT a blank line (GH-20769) https://github.com/python/cpython/commit/e3ce3bba9277a7c4cfde5aaf6269b6c68f334176

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Change by miss-islington : -- nosy: +miss-islington nosy_count: 7.0 -> 8.0 pull_requests: +19991 pull_request: https://github.com/python/cpython/pull/20795 ___ Python tracker

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Pablo Galindo Salgado added the comment: New changeset 896f4cf63f9ab93e30572d879a5719d5aa2499fb by Lysandros Nikolaou in branch 'master': bpo-40847: Consider a line with only a LINECONT a blank line (GH-20769) https://github.com/python/cpython/commit/896f4cf63f9ab93e30572d879a5719d5aa2499fb

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Change by Lysandros Nikolaou : -- keywords: +patch pull_requests: +19967 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20769 ___ Python tracker

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Guido van Rossum added the comment: To be clear, I consider it a bug. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Adam Williamson added the comment: I'm not the best person to ask what I'd "consider" to be a bug or not, to be honest. I'm just a Fedora packaging guy trying to make our packages build with Python 3.9 :) If this is still an important question, I'd suggest asking the folks from the Black

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Guido van Rossum added the comment: Sure looks like a tokenizer issue to me. For example this is broken in both versions: pass \ pass It complains about an unexpected indent, but it should really be considered a blank line broken in two -- a backslash is supposed to just erase itself

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Lysandros Nikolaou added the comment: This is limited to cases where the line continuation character is on an otherwise empty line. For example this works correctly: $ cat t.py print("hello world") print("hello world 2") \ print("hello world 3") $ ./python.exe t.py hello world hello world 2

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Change by Pablo Galindo Salgado : -- nosy: +gvanrossum, lys.nikolaou ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Change by Christian Heimes : -- nosy: +christian.heimes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Change by Christian Heimes : -- nosy: +benjamin.peterson, brett.cannon, pablogsal, yselivanov versions: +Python 3.10 ___ Python tracker ___

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

New submission from Adam Williamson : While debugging issues with the black test suite in Python 3.9, I found one which black upstream says is a Cpython issue, so I'm filing it here. Reproduction is very easy. Just use this four-line tester: print("hello, world") \ print("hello,