summaryrefslogtreecommitdiffstats
path: root/Lib/idlelib
diff options
context:
space:
mode:
authorPablo Galindo Salgado <Pablogsal@gmail.com>2022-01-27 00:16:50 (GMT)
committerGitHub <noreply@github.com>2022-01-27 00:16:50 (GMT)
commitc7af838805ddf52320bce3d5978bfdd37eed1b3a (patch)
treeacfad9dcbd811d8063ec588781e4ecd83575c185 /Lib/idlelib
parent171fdf2162130bc8c748173bc8eef184b21f5a08 (diff)
downloadcpython-c7af838805ddf52320bce3d5978bfdd37eed1b3a.zip
cpython-c7af838805ddf52320bce3d5978bfdd37eed1b3a.tar.gz
cpython-c7af838805ddf52320bce3d5978bfdd37eed1b3a.tar.bz2
[3.10] bpo-46502: Remove "How do I tell incomplete input" from FAQ (GH-30925) (GH-30933)
Since, - Py_CompileString no longer allows to distinguish "incomplete input" from "invalid input" - there is no alternative solution available from the Python C API due to how the new parser works (rewritten in 3.9) - the only supported way is to manually import the codeop module from C and use its API as IDLE does, and accept its own complications it is desirable to remove this Q&A from the official FAQ.. (cherry picked from commit f0a648152f2d8011f47cc49873438ebaf01d3f82) Co-authored-by: Mateusz Łoskot <mateusz@loskot.net> Co-authored-by: Mateusz Łoskot <mateusz@loskot.net>
Diffstat (limited to 'Lib/idlelib')
0 files changed, 0 insertions, 0 deletions