bpo-5028: Fix up rest of documentation for tokenize documenting line (GH-13686)

https://bugs.python.org/issue5028

diff --git a/Doc/library/tokenize.rst b/Doc/library/tokenize.rst
index c89d3d4b082f5ec59bca24586e6f2f11f11ec97a..b208ba46d17d99de7b4835697ea923fb92f4ff44 100644 (file)
--- a/Doc/library/tokenize.rst
+++ b/Doc/library/tokenize.rst
@@ -39,8 +39,8 @@ The primary entry point is a :term:`generator`:
    column where the token begins in the source; a 2-tuple ``(erow, ecol)`` of
    ints specifying the row and column where the token ends in the source; and
    the line on which the token was found. The line passed (the last tuple item)
-   is the *physical* line; continuation lines are included.  The 5 tuple is
-   returned as a :term:`named tuple` with the field names:
+   is the *physical* line.  The 5 tuple is returned as a :term:`named tuple`
+   with the field names:
    ``type string start end line``.
 
    The returned :term:`named tuple` has an additional property named

diff --git a/Lib/lib2to3/pgen2/tokenize.py b/Lib/lib2to3/pgen2/tokenize.py
index 0f9fde3fb0d5f66a04dfb0b933995bea864c2d6f..7924ff3cd582fcca203cc695b08606fc48d421df 100644 (file)
--- a/Lib/lib2to3/pgen2/tokenize.py
+++ b/Lib/lib2to3/pgen2/tokenize.py
@@ -346,7 +346,7 @@ def generate_tokens(readline):
     column where the token begins in the source; a 2-tuple (erow, ecol) of
     ints specifying the row and column where the token ends in the source;
     and the line on which the token was found. The line passed is the
-    physical line; continuation lines are included.
+    physical line.
     """
     lnum = parenlev = continued = 0
     contstr, needcont = '', 0

diff --git a/Lib/tokenize.py b/Lib/tokenize.py
index 738fb71d188b478c417c3a697eb97d4072a09305..1aee21b5e18fa716dfaa5306fc6aa8a96d253641 100644 (file)
--- a/Lib/tokenize.py
+++ b/Lib/tokenize.py
@@ -415,7 +415,7 @@ def tokenize(readline):
     column where the token begins in the source; a 2-tuple (erow, ecol) of
     ints specifying the row and column where the token ends in the source;
     and the line on which the token was found.  The line passed is the
-    physical line; continuation lines are included.
+    physical line.
 
     The first token sequence will always be an ENCODING token
     which tells you which encoding was used to decode the bytes stream.