Skip to content

[3.10] bpo-46502: Remove "How do I tell incomplete input" from FAQ (GH-30925) #30933

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 27, 2022

Conversation

pablogsal
Copy link
Member

@pablogsal pablogsal commented Jan 26, 2022

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 f0a6481)

Co-authored-by: Mateusz Łoskot [email protected]

https://bugs.python.org/issue46502

…ythonGH-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..
(cherry picked from commit f0a6481)

Co-authored-by: Mateusz Łoskot <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation in the Doc dir skip news
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants