gh-105879: Add support for keyword arguments to eval and exec#105885
gh-105879: Add support for keyword arguments to eval and exec#105885JelleZijlstra merged 8 commits into
Conversation
|
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
Sorry, something went wrong.
Sorry, something went wrong.
hauntsaninja
left a comment
There was a problem hiding this comment.
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)
Sorry, something went wrong.
|
Does this need a doc change? |
Sorry, something went wrong.
|
@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 |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
…ython#105885) Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
edited by bedevere-bot
LoadingUh oh!
There was an error while loading. Please reload this page.
Copy link Copy MarkdownSorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.