-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
gh-98586: add whatsnew entry covering limited-API outgoing vector calls, related documentation fix #99056
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
PR python#98587 addressing issue python#98586 lacked a "what's new" entry. While making those changes, I noticed an inconsistency in how ``PY_VECTORCALL_ARGUMENTS_OFFSET`` is declared in the underlying Sphinx markup when compared to other macro constants like ``Py_TPFLAGS_HAVE_VECTORCALL``. This PR fixes that as well, which should connect a few currently broken cross-references
FYI, you should mention in the PR title (which is also the default commit message) what you are adding a What's New entry for... |
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.
Seems like these should be changed to use equivalent roles from the appropriate domain, though I'm not sure why the Python domain has data/const but the C domain doesn't, despite C actually having "real" constants and Python only having a convention, nor what the reason was for using construct from the "wrong" domain originally...
@AA-Turner , any expert insight here?
Misc/NEWS.d/next/Core and Builtins/2022-10-24-10-30-30.gh-issue-98586.Tha5Iy.rst
Show resolved
Hide resolved
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
@CAM-Gerlach -- I updated the PR title (sorry) and merged the change with the missing article. I am hesitant to make the domain-related changes you requested. Part of the reason is that I am following the pattern that generally seems to be used for macro constants. For example look at how |
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.
Okay, that makes sense for now I guess. In that case, LGTM, aside from one comment
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
Incorporated, thanks. |
Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com>
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.
LGTM, thanks!
Related: we should really update the docs on best practice for writing exension modules using the Limited C API (there is already an issue for this).
PR #98587 addressing issue #98586 lacked a "what's new" entry.
While making those changes, I noticed an inconsistency in how
PY_VECTORCALL_ARGUMENTS_OFFSET
is declared in the underlying Sphinx markup when compared to other macro constants likePy_TPFLAGS_HAVE_VECTORCALL
. This PR fixes that as well, which should connect a few currently broken cross-references