-
-
Notifications
You must be signed in to change notification settings - Fork 32k
gh-87771: Improve documentation of eval() #100003
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
environment where :func:`eval` is called. If only the *globals* argument is | ||
provided, the local namespace defaults to *globals*. | ||
|
||
Before evaluation, the special key ``"__builtins__"`` is searched for in the |
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.
Not too certain about quoting the key, and perhaps it could be non-literal and just "builtins" instead, but I'll defer judgement here.
Co-authored-by: Irit Katriel <1055913+iritkatriel@users.noreply.github.com>
✅ Deploy Preview for python-cpython-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
This has been superseded by #119235 and its follow-ups (the exec/eval docs have also been more generally updated for PEP 667, hence the conflicts on this PR) Thanks for the efforts here, even though they ultimately weren't merged. |
Clone of the eval section of #25039 with conflicts fixed and some changes in phrasing, but wording kept mostly the same.
See this for discussion on 'condition list' and why it was changed to 'expression input'.
https://docs.python.org/dev/library/functions.html#eval
Co-authored-by: Cong Ma cong.ma@obspm.fr