From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Wed, 15 Apr 2026 16:15:31 +0000 (+0200) Subject: [3.13] gh-100305: Deemphasize that `ast.literal_eval` is safe in `eval` documentation... X-Git-Url: http://git.ipfire.org/index.cgi?a=commitdiff_plain;h=9c2db8144ed15f0b57fdb90ed7c7e8c362debd28;p=thirdparty%2FPython%2Fcpython.git [3.13] gh-100305: Deemphasize that `ast.literal_eval` is safe in `eval` documentation (GH-100326) (#148421) (cherry picked from commit b3b0cef0c2aacdc616fa48674552ab1e34553835) Co-authored-by: Ram Vikram Singh Co-authored-by: Éric --- diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst index 35a9c1356e1a..39f6fc7bb3ed 100644 --- a/Doc/library/functions.rst +++ b/Doc/library/functions.rst @@ -629,7 +629,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