From 0f58608229a784a3465ef6bb5ef82c96a32d9bb2 Mon Sep 17 00:00:00 2001 From: Ram Vikram Singh Date: Sun, 12 Apr 2026 08:37:42 +0530 Subject: [PATCH] gh-100305: Deemphasize that `ast.literal_eval` is safe in `eval` documentation (GH-100326) (cherry picked from commit b3b0cef0c2aacdc616fa48674552ab1e34553835) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Ram Vikram Singh Co-authored-by: Éric --- Doc/library/functions.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst index 35a9c1356e1a13..39f6fc7bb3ed2e 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