You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This could happen when the stub loader is created, since the .so exists at that point. It would ensure that people don't accidentally build hpy universal binaries that only work because our implementations currently have cpyext (or are CPython)
The text was updated successfully, but these errors were encountered:
Another option is to set up compilation so that any use of Python.h will fail. This could be done by setting the include macro and creating a "fake" Python.h. Maybe both methods are needed to actually prove the binary is truly universal.
This could happen when the stub loader is created, since the
.so
exists at that point. It would ensure that people don't accidentally build hpy universal binaries that only work because our implementations currently have cpyext (or are CPython)The text was updated successfully, but these errors were encountered: