From 1f5569824f52e0e03d6ae6020233c0e025ce5008 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Sat, 9 Jun 2018 17:12:24 -0700 Subject: [PATCH] bpo-33766: Document that end of file or string is a newline (GH-7383) (cherry picked from commit 0aa17ee6a76df0946d42e7657a501f1862065a22) Co-authored-by: Ammar Askar --- Doc/reference/lexical_analysis.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/Doc/reference/lexical_analysis.rst b/Doc/reference/lexical_analysis.rst index 6d093dcc2a..a8619967e7 100644 --- a/Doc/reference/lexical_analysis.rst +++ b/Doc/reference/lexical_analysis.rst @@ -47,11 +47,12 @@ Physical lines -------------- A physical line is a sequence of characters terminated by an end-of-line -sequence. In source files, any of the standard platform line termination -sequences can be used - the Unix form using ASCII LF (linefeed), the Windows -form using the ASCII sequence CR LF (return followed by linefeed), or the old -Macintosh form using the ASCII CR (return) character. All of these forms can be -used equally, regardless of platform. +sequence. In source files and strings, any of the standard platform line +termination sequences can be used - the Unix form using ASCII LF (linefeed), +the Windows form using the ASCII sequence CR LF (return followed by linefeed), +or the old Macintosh form using the ASCII CR (return) character. All of these +forms can be used equally, regardless of platform. The end of input also serves +as an implicit terminator for the final physical line. When embedding Python, source code strings should be passed to Python APIs using the standard C conventions for newline characters (the ``\n`` character, -- 2.50.1