[issue29968] Document that no characters are allowed to proceed \ in explicit line joining

Jim Fasarakis-Hilliard added the comment: Gotcha, thanks for the input, David. I'll leave it to you to decide if the sentence on the trailing comments warrants removal. -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python

[issue29968] Document that no characters are allowed to proceed \ in explicit line joining

R. David Murray added the comment: I don't see any omission, myself. Keep in mind that the language reference is as much or more of a specification as it is a reference, so we tend to try to use the minimum language that precisely describes the expected behavior. Which is why I suggested that

[issue29968] Document that no characters are allowed to proceed \ in explicit line joining

Jim Fasarakis-Hilliard added the comment: Ah, yes, the Ref. Manual, not the devguide, silly mistake. It definitely isn't a documentation bug (the documentation doesn't state something wrong) as much as I think it might be a slight omission. I really wasn't aware of how strict the tokenizer is

[issue29968] Document that no characters are allowed to proceed \ in explicit line joining

Martin Panter added the comment: I think he means make something like the following legal, where dots (.) indicate space characters: a.=.\. b At the moment it is a SyntaxError: >>> a = \ File "", line 1 a = \ ^ SyntaxError: unexpected character after line continuation cha

[issue29968] Document that no characters are allowed to proceed \ in explicit line joining

R. David Murray added the comment: I think you meant "the language reference" rather than "the devguide". The sentence about the comment is redundant with the preceding line that says that the thing that results in a join is a physical line that ends with a backslash ("that is not part of..."

[issue29968] Document that no characters are allowed to proceed \ in explicit line joining

R. David Murray added the comment: I also have no idea what your comment about stripping white space is in reference to ;) -- ___ Python tracker ___

[issue29968] Document that no characters are allowed to proceed \ in explicit line joining

Jim Fasarakis-Hilliard added the comment: Alternatively, stripping all white-space that proceed `\` could be considered if it seems like a good idea. -- ___ Python tracker ___ _

[issue29968] Document that no characters are allowed to proceed \ in explicit line joining

New submission from Jim Fasarakis-Hilliard: After looking through the code, the tokenizer only allows a new line character to proceed `\` in explicit line joining [1]. The Devguide section on it [2] actually states many of the limitations of using `\` but not directly that nothing is allowed a