Visitar URL original
gh-100305: Deemphasize that `ast.literal_eval` is safe in `eval` documentation by ramvikrams · Pull Request #100326 · python/cpython · GitHub
Skip to content
Merged
Changes from 1 commit
Commits
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
Prev Previous commit
Next Next commit
don't scare quotes safely, just say to
Co-authored-by: Éric <merwok@netwok.org>
  • Loading branch information
gpshead and merwok authored Apr 12, 2026
commit e388fd46394ea743bc08e0697b363e240530891e
2 changes: 1 addition & 1 deletion Doc/library/functions.rst
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 to evaluate strings
with expressions containing only literals.

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