Skip to content

gh-100305: Deemphasize that ast.literal_eval is safe in eval documentation #100326

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.

Sign up for GitHub

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
gpshead merged 6 commits into from
Apr 12, 2026
+1 −1
Merged

gh-100305: Deemphasize that ast.literal_eval is safe in eval documentation #100326

Changes from 4 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
45e57be
changed the doc for literal_eval in eval
ramvikrams Dec 17, 2022
c05387b
Update functions.rst
ramvikrams Dec 17, 2022
da1f416
Update functions.rst
ramvikrams Dec 18, 2022
d05eacc
Update functions.rst
ramvikrams Dec 20, 2022
e388fd4
don't scare quotes safely, just say to
gpshead Apr 12, 2026
f6d3883
Merge branch 'main' into t12
gpshead Apr 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Doc/library/functions.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -554,7 +554,7 @@ are always available. They are listed here in alphabetical order.
If the given source is a string, then leading and trailing spaces and tabs
are stripped.

See :func:`ast.literal_eval` for a function that can safely evaluate strings
See :func:`ast.literal_eval` for a function that can "safely" evaluate strings
with expressions containing only literals.
Comment thread
gpshead marked this conversation as resolved.
Outdated

.. audit-event:: exec code_object eval
Expand Down