René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Allow eval and exec to take keyword arguments","articleBody":"# Feature or enhancement\r\n\r\nAllow for `globals` and `locals` to be passed in as keyword arguments to `exec` and `eval`.\r\n\r\n# Pitch\r\n\r\n`exec` and `eval` both can take `globals` and `locals` as positional arguments. \r\nThe built-in functions documentation shows the argument defaults, and _every time_ I have the documentation open and am writing these, I default to keyword arguments, and it fails because the arguments are positional-only.\r\n\r\nFor functions like this that might only be present in a handful of places, kwargs give a good way to document what parameters each argument is referring to. I don't think that in a universe in which we were introducing `eval`/`exec` now that we would explicitly disallow kwargs.\r\n\r\n# Previous discussion\r\n\r\nI sent [this email](https://mail.python.org/archives/list/python-ideas@python.org/thread/AD37KVC4CP4HQD4D7VUJTCWSP4LKEZYB/) to `python-ideas`\r\n\r\n# Extra Links\r\n\r\n[Here is an implementation](https://github.com/rtpg/cpython/commit/c4368ef213a64297954fbca4f5308d69409d6a4b), which just consists in changing the argument clinic config and rerunning. I set up some very basic kwarg tests mostly to test the case of \"locals provided but globals not provided\", but fortunately the existing implementations already handled this cleanly!\r\n\r\n\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-105885\n* gh-121831\n* gh-121852\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/rtpg","@type":"Person","name":"rtpg"},"datePublished":"2023-06-17T02:43:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/105879/cpython/issues/105879"}