GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||
GeezerVison is showing github.com — gh-74929: locals() documentation update for PEP 667 by ncoghlan · Pull Request #118265 · python/cpython Conversation
|
|
DO-NOT-MERGE label added, as this should only be merged after the PEP 667 implementation in #115153 has been completed and merged. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Wouldn't it better to convert the pull request back to a draft? GitHub automatically prevents you from merging those. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Good point, done (enough years of experience where draft PRs weren't available that I still forget to use them when appropriate) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| implicitly refreshed by other operations, such as calling ``locals()`` | ||
| again. Obtaining the legacy CPython behaviour now requires explicit | ||
| calls to update the initially returned dictionary with the results | ||
| of subsequent calls to ``locals()``. |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I plan to eventually replace the latter two sentences here with something like "For details, refer to the 'Python 3.13 porting guide'" (with a link to the relevant part of the 3.13 What's New document). That will be in a later PR that adds an initial version of the What's New update for PEP 667, though.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.