Allow building the C extension on GraalPy and running tests with it.

[timfel]

With these changes we can build the HPy C extension on GraalPy and run the tests.

[hodgestar]

What does is mean that GraalPy no longer has its own universal module? Does it now full support this via its CPython C API? Is this a good or bad thing? :)

What is the plan for the tests that fail on GraalPy? Slowly fix them somehow?

[mattip]

The previous PR merged to main was green, and now valgrind and python2.7 is failing. What changed?

[timfel]

The previous PR merged to main was green, and now valgrind and python2.7 is failing. What changed?

The 2.7 is just that i added a skip using sys.implementation without guarding for 2.7

The valgrind issue seems this: https://github.com/hpyproject/hpy/actions/runs/14363896576/job/40272010157?pr=484#step:6:13

python3 setup.py build_clib -f build_ext -if
/home/runner/work/hpy/hpy/.eggs/setuptools_scm-8.2.0-py3.9.egg/setuptools_scm/_integration/setuptools.py:31: RuntimeWarning: 
ERROR: setuptools==58.1.0 is used in combination with setuptools-scm>=8.x

Your build configuration is incomplete and previously worked by accident!
setuptools-scm requires setuptools>=61

Looking into it 👀

[timfel]

For valgrind I opened https://github.com/hpyproject/hpy/pull/485/files

[mattip]

#485 is in, do you want to rebase/merge to get that here?

[timfel]

What does is mean that GraalPy no longer has its own universal module? Does it now full support this via its CPython C API? Is this a good or bad thing? :)

It's a pretty good test case for our cpyext layer :)

What is the plan for the tests that fail on GraalPy? Slowly fix them somehow?

The nice thing is that these are pretty good small tests for our cpyext and they probably expose issues that manifest in other larger C extensions in a less reproducible way, so yes, I plan to pick at these and get them working. We used to have more working in fact, but we regressed a bit recently, but I would like to get this in sooner rather than later and continue with follow-up PRs.

[hodgestar]

The changes look good from my side. Happy to review again later once tests are passing.

[timfel]

@mattip do these need to run as apptests in pypy?

[timfel]

@mattip same question as for test_cpy_compat, do these need to run as apptests in pypy? If so I will pull the skip into the body of the methods like in test_object.py etc

[timfel]

The changes look good from my side. Happy to review again later once tests are passing.

Thanks, tests are passing now, just need someone to check if this'll work for PyPy apptests.

[mattip]

All the test_* files are run untranslated on PyPy, so we cannot import pytest in the global level. On the other hand, it only becomes an issue if we pull latest HPy HEAD into PyPy, which will only happen if there is more development of PyPy + HPy. I am not sure that will happen, so I think we can merge the code as you have it here and refactor for PyPy when/if needed.

[mattip]

It might be nice to make a release of HPy since HEAD includes the changes needed for Cython.