diff options
| author | Petr Viktorin <encukou@gmail.com> | 2025-03-17 16:05:47 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-17 16:05:47 (GMT) |
| commit | 30d52058493e07fd1d3efea960482f4001bd2f86 (patch) | |
| tree | c4e4087f551e9bef40968f5b73d2e44be867f435 /Doc/tutorial | |
| parent | 863d54cbaf6c0b45fff691ab275515c1483ad68d (diff) | |
| download | cpython-30d52058493e07fd1d3efea960482f4001bd2f86.zip cpython-30d52058493e07fd1d3efea960482f4001bd2f86.tar.gz cpython-30d52058493e07fd1d3efea960482f4001bd2f86.tar.bz2 | |
gh-116666: Add "token" glossary term (GH-130888)
Add glossary entry for `token`, and link to it.
Avoid talking about tokens in the SyntaxError intro (errors.rst); at this point
tokenization is too much of a technical detail. (Even to an advanced reader,
the fact that a *single* token is highlighted isn't too relevant. Also, we don't
need to guarantee that it's a single token.)
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Diffstat (limited to 'Doc/tutorial')
| -rw-r--r-- | Doc/tutorial/errors.rst | 11 | ||||
| -rw-r--r-- | Doc/tutorial/interactive.rst | 8 |
2 files changed, 10 insertions, 9 deletions
diff --git a/Doc/tutorial/errors.rst b/Doc/tutorial/errors.rst index c01cb8c..bfb281c 100644 --- a/Doc/tutorial/errors.rst +++ b/Doc/tutorial/errors.rst @@ -24,11 +24,12 @@ complaint you get while you are still learning Python:: SyntaxError: invalid syntax The parser repeats the offending line and displays little arrows pointing -at the token in the line where the error was detected. The error may be -caused by the absence of a token *before* the indicated token. In the -example, the error is detected at the function :func:`print`, since a colon -(``':'``) is missing before it. File name and line number are printed so you -know where to look in case the input came from a script. +at the place where the error was detected. Note that this is not always the +place that needs to be fixed. In the example, the error is detected at the +function :func:`print`, since a colon (``':'``) is missing just before it. + +The file name (``<stdin>`` in our example) and line number are printed so you +know where to look in case the input came from a file. .. _tut-exceptions: diff --git a/Doc/tutorial/interactive.rst b/Doc/tutorial/interactive.rst index 4e054c4..00e705f 100644 --- a/Doc/tutorial/interactive.rst +++ b/Doc/tutorial/interactive.rst @@ -37,10 +37,10 @@ Alternatives to the Interactive Interpreter This facility is an enormous step forward compared to earlier versions of the interpreter; however, some wishes are left: It would be nice if the proper -indentation were suggested on continuation lines (the parser knows if an indent -token is required next). The completion mechanism might use the interpreter's -symbol table. A command to check (or even suggest) matching parentheses, -quotes, etc., would also be useful. +indentation were suggested on continuation lines (the parser knows if an +:data:`~token.INDENT` token is required next). The completion mechanism might +use the interpreter's symbol table. A command to check (or even suggest) +matching parentheses, quotes, etc., would also be useful. One alternative enhanced interactive interpreter that has been around for quite some time is IPython_, which features tab completion, object exploration and |