diff options
author | Pablo Galindo Salgado <Pablogsal@gmail.com> | 2022-01-27 00:16:44 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-01-27 00:16:44 (GMT) |
commit | dafada393f9a790461430e2493ea1379e938b51a (patch) | |
tree | d8e423bcf7eb2aaa4268c726a9bc67c5d0fc087d /Doc/library | |
parent | ff11effab7ae10b57719c066ee49b52d3991ead3 (diff) | |
download | cpython-dafada393f9a790461430e2493ea1379e938b51a.zip cpython-dafada393f9a790461430e2493ea1379e938b51a.tar.gz cpython-dafada393f9a790461430e2493ea1379e938b51a.tar.bz2 |
[3.9] bpo-46502: Remove "How do I tell incomplete input" from FAQ (GH-30925) (GH-30934)
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 'Doc/library')
0 files changed, 0 insertions, 0 deletions