[issue42007] Line continuation after Boolean operation

Eric V. Smith added the comment: Agreed that this isn't likely to change. If you have a concrete proposal for how the language parsing rules would change in order to support this, you should post it to the python-ideas mailing list. If that discussion results in a consensus, then we can

[issue42007] Line continuation after Boolean operation

Raymond Hettinger added the comment: Sorry, I don't think this proposal has a chance. Python doesn't require statement terminators like ";" in C. Accordingly, it needs to have a clean and consistent rule to close a statement. The rule that has worked well for us it that a statement is

[issue42007] Line continuation after Boolean operation

veganaiZe added the comment: Actually, I can do it the second way. I must have typo'd when testing (my apologies)... But I'd still like to do it the first way. ☺ -- ___ Python tracker

[issue42007] Line continuation after Boolean operation

New submission from veganaiZe : I can't do something like this (regarding the `or`)... if (not position.x == 0 and velocity == -1) or (not position.x == 500 and velocity == 1) Nor this... if (not position.x == 0 and velocity == -1) or ( not position.x == 500