mirror of
https://github.com/python/cpython
synced 2024-10-06 13:18:00 +00:00
e5fe509054
When trying to extract the error line for the error message there
are two distinct cases:
1. The input comes from a file, which means that we can extract the
error line by using `PyErr_ProgramTextObject` and which we already
do.
2. The input does not come from a file, at which point we need to get
the source code from the tokenizer:
* If the tokenizer's current line number is the same with the line
of the error, we get the line from `tok->buf` and we're ready.
* Else, we can extract the error line from the source code in the
following two ways:
* If the input comes from a string we have all the input
in `tok->str` and we can extract the error line from it.
* If the input comes from stdin, i.e. the interactive prompt, we
do not have access to the previous line. That's why a new
field `tok->stdin_content` is added which holds the whole input for the
current (multiline) statement or expression. We can then extract the
error line from `tok->stdin_content` like we do in the string case above.
Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>
|
||
|---|---|---|
| .. | ||
| asdl.py | ||
| asdl_c.py | ||
| myreadline.c | ||
| parser.c | ||
| peg_api.c | ||
| pegen.c | ||
| pegen.h | ||
| Python.asdl | ||
| string_parser.c | ||
| string_parser.h | ||
| token.c | ||
| tokenizer.c | ||
| tokenizer.h | ||