[issue46293] Typo in specifying escape sequence

Zachary Ware added the comment: The table could stand some clarification; `\newline` is the only example that is not showing exactly the characters that one would see when looking at source code and which doesn't have an explanatory note. There's also the additional wrinkle that `\CR`,

[issue46293] Typo in specifying escape sequence

Steven D'Aprano added the comment: Serhiy is correct. The table is correct, \n can be found further down the table, the first entry is backslash newline, as it says. -- nosy: +steven.daprano resolution: -> not a bug stage: -> resolved status: open -> closed

[issue46293] Typo in specifying escape sequence

Serhiy Storchaka added the comment: No, it is a backslash following by a newline. -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue46293] Typo in specifying escape sequence

New submission from Preetham Nanjappa : See section "2.4.1. String and Bytes literals" of 3.10.1 documentation. https://docs.python.org/3.10/reference/lexical_analysis.html#string-and-bytes-literals Escape Sequence table. First line. `\newline` should have been `\n` -- assignee: