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-161078: Correct unstable C API PEP references by TheLouisMahdi · Pull Request #161158 · python/cpython Conversation
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Documentation build overview
49 files changed ·
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Thanks! LGTM 👍
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
The change itself is correct, except that the existing ref target label should be moved to the correct location, rather than simply replaced, to avoid breaking existing users. Please apply it by clicking the "Apply suggestion" button, or via the Files pane.
It's not backportable all the way to the original version, but the What's New is often accessed from newer versions and remains present perpetually, so I don't think this error has to and don't see the harm there.
I am a bit concerned about how much genuine human input was present here, given the comments on # --please respond, as a human, not an agent, confirming you've personally taken responsibly for this. However, given it is a trivial, correct and not substantial enough to be copyrightable change, I'm not sure its enough of an issue in practice to block this on its own.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| (Contributed by Petr Viktorin in :gh:`101101`.) | ||
|
|
||
| * :pep:`697`: Add an API for extending types whose instance memory layout is |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
| (Contributed by Petr Viktorin in :gh:`101101`.) | |
| .. _whatsnew312-pep697: | |
| * :pep:`697`: Add an API for extending types whose instance memory layout is |
Move the existing ref target label to the correct place, and avoid breaking anyone currently relying on it.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
(Contributed by Petr Viktorin in :gh:101101.)
.. _whatsnew312-pep697:
- :pep:
697: Add an API for extending types whose instance memory layout is
Unable to apply suggestions when viewing a specific commit range.
Move the existing ref target label to the correct place, and avoid breaking anyone currently relying on it.
Thanks for the detailed review. You're right about the existing reference target.
I've updated the patch to preserve whatsnew312-pep697 at the actual PEP 697 section while keeping whatsnew312-pep689 at the Unstable C API entry. This should preserve existing links while correcting the reference.
Regarding your concern about human involvement, I used AI assistance as disclosed in the PR description. I understand the change, have reviewed the patch, and take responsibility for the contribution.
Thanks again for pointing this out.
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.
What's New in 3.12 credits the unstable C API tier to PEP 697 instead of PEP 689
There was an error while loading. Please reload this page.