Uh oh!
There was an error while loading. Please reload this page.
gh-100305: Deemphasize that ast.literal_eval is safe in eval documentation - #100326
Conversation
| See :func:`ast.literal_eval` for a function that can safely evaluate strings | ||
| with expressions containing only literals. | ||
| .. versionchanged:: 3.11 |
There was a problem hiding this comment.
I'm not so sure about saying 'version changed', as it seems to imply that only 3.11 has the change, but 3.10 also has it as it was backported (see PR). I'd say it's okay to just keep the original format and adjust the wording.
ast.literal_eval is still referred to as safe by the documentation for evalast.literal_eval is safe in eval documentationUh oh!
There was an error while loading. Please reload this page.
This PR is stale because it has been open for 30 days with no activity. |
Co-authored-by: Éric <merwok@netwok.org>
Uh oh!
There was an error while loading. Please reload this page.
Thanks @ramvikrams for the PR, and @gpshead for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
…` documentation (pythonGH-100326) (cherry picked from commit b3b0cef) Co-authored-by: Ram Vikram Singh <ramvikrams243@gmail.com> Co-authored-by: Éric <merwok@netwok.org>
GH-148420 is a backport of this pull request to the 3.14 branch. |
…` documentation (pythonGH-100326) (cherry picked from commit b3b0cef) Co-authored-by: Ram Vikram Singh <ramvikrams243@gmail.com> Co-authored-by: Éric <merwok@netwok.org>
GH-148421 is a backport of this pull request to the 3.13 branch. |
…` documentation (python#100326) Co-authored-by: Éric <merwok@netwok.org>
gh-100305: Changed the doc referencing to
literal_evalin eval as it was misleading asliteral_evalwas said safe