diff options
author | Mateusz Ĺoskot <mateusz@loskot.net> | 2022-01-26 23:49:06 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-01-26 23:49:06 (GMT) |
commit | f0a648152f2d8011f47cc49873438ebaf01d3f82 (patch) | |
tree | a38d9748926c254a5b3966d4131a88089642c341 /Tools/unittestgui/README.txt | |
parent | 13194084b40fe6579a70248b7be0665ff4f08374 (diff) | |
download | cpython-f0a648152f2d8011f47cc49873438ebaf01d3f82.zip cpython-f0a648152f2d8011f47cc49873438ebaf01d3f82.tar.gz cpython-f0a648152f2d8011f47cc49873438ebaf01d3f82.tar.bz2 |
bpo-46502: Remove "How do I tell incomplete input" from FAQ (GH-30925)
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.
Diffstat (limited to 'Tools/unittestgui/README.txt')
0 files changed, 0 insertions, 0 deletions