-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
bpo-32758: warn that a couple ast functions can crash the interpreter #5960
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
Conversation
Got approval for the wording from @serhiy-storchaka in the issue itself, but he also pointed out that there are implicit uses of the troublesome functions in various other places, so the comment needs to spread out a bit more before this PR can get merged. |
Thanks @brettcannon for the PR 🌮🎉.. I'm working now to backport this PR to: 2.7, 3.6, 3.7. |
…the interpreter (pythonGH-5960) (cherry picked from commit 7a7f100) Co-authored-by: Brett Cannon <brettcannon@users.noreply.github.com>
GH-6041 is a backport of this pull request to the 3.7 branch. |
Sorry, @brettcannon, I could not cleanly backport this to |
…the interpreter (pythonGH-5960) (cherry picked from commit 7a7f100) Co-authored-by: Brett Cannon <brettcannon@users.noreply.github.com>
GH-6042 is a backport of this pull request to the 3.6 branch. |
…the interpreter (pythonGH-5960) (cherry picked from commit 7a7f100) Co-authored-by: Brett Cannon <brettcannon@users.noreply.github.com>
GH-16565 is a backport of this pull request to the 2.7 branch. |
Both
ast.parse()
andast.literal_eval()
can trigger a segfault with the appropriate string input due to the recursion depth limit of the AST compiler.https://bugs.python.org/issue32758