-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
gh-93274: Disable Limited API tests with Py_TRACE_REFS #95796
Conversation
@@ -1,3 +1,16 @@ | |||
#include "pyconfig.h" // Py_TRACE_REFS | |||
|
|||
#ifdef Py_TRACE_REFS |
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.
I would suggest to move this #ifdef in _testcapimodule.c instead.
// Py_TRACE_REFS is incompatible with Limited API | ||
#include "parts.h" | ||
int | ||
_PyTestCapi_Init_VectorcallLimited(PyObject *m) { |
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.
I suggest putting an #ifdef on the _PyTestCapi_Init_VectorcallLimited() call in _testcapimodole.c instead of defining a no-op function.
Maybe define somewhere a macro to decide if vectorcall is tested or not? Something like:
#ifndef Py_TRACE_REFS
# define TEST_VECTORCALL
#endif
If the tests pass, I'll merge this as is and make it better later. I'd like to make testing limited API as smooth as possible, which'll be much easier without the pressure of a red buildbot. |
This should fix the Py_TRACE_REFS buildbot.
(In the future we'll need a better way to write limited API tests.)