-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
gh-105879: Add support for keyword arguments to eval and exec #105885
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
rtpg
commented
Jun 17, 2023
•
edited by bedevere-bot
Loading
edited by bedevere-bot
- Issue: Allow eval and exec to take keyword arguments #105879
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
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.
Thanks for suggesting and adding this feature! I've definitely confused the ordering of these before :-) This looks good to me (although I think I still have a vague preference for keeping the source
argument positional-only)
Does this need a doc change? |
@iritkatriel i believe that the docstring changes (derived from the arg clinic changes) are sufficient, as I did not see anything being explicit about positional-only-ness beyond that |
I fixed the (trivial) merge conflict, undid an unnecessary formatting change, and added a documentation note as @iritkatriel suggested. I'll merge the PR in a bit so we can get this change into 3.13. |
Thinking about it again I agree with @hauntsaninja's suggestion above that we should leave the first argument positional-only. I'll make that change. |
…ython#105885) Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>