-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
gh-142568: Fix eval() docs to use 'source' parameter name #142644
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.
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
Conversation
|
CC @JelleZijlstra (Since you merged 2770d5c) |
StanFromIreland
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Thanks @Joshua-Ward1 for the PR, and @JelleZijlstra for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
…onGH-142644) (cherry picked from commit c865ab3) Co-authored-by: Joshua Ward <joshie@flewognetworks.wales>
…onGH-142644) (cherry picked from commit c865ab3) Co-authored-by: Joshua Ward <joshie@flewognetworks.wales>
|
GH-142669 is a backport of this pull request to the 3.14 branch. |
|
GH-142670 is a backport of this pull request to the 3.13 branch. |
Summary
Fixes an inconsistency in the documentation for
eval()where the parameterwas referred to as “expression” instead of “source”, which does not match
the function signature.
Rationale
The function signature and parameter description already use
source.Updating the prose ensures consistency and avoids confusion for readers.
Changes
Doc/library/functions.rstto consistently refer to thesourceparameter in the
eval()documentation.Testing
Not applicable — documentation-only change.
Related issue
📚 Documentation preview 📚: https://cpython-previews--142644.org.readthedocs.build/