TEST: test passes on PyPy macOS

[mattip]

Description

test_cross_module_exception_translator now passes on macOS + PyPy, see PyPy-specific CI run. Probably not important enough for a changelog blurb?

Suggested changelog entry:

[rwgk]

@mattip What is different between e.g.

• https://github.com/pybind/pybind11/actions/runs/13917408994/job/38942898299?pr=5569
• https://github.com/pypy/binary-testing/actions/runs/13910062694/job/38922125525

?

Do we need to update our .github/workflows/ci.yml here?

It'd be great if you could drop pypy-3.8, pypy-3.9, and update the jobs for pypy-3.10 and pypy-3.11 so that they are most useful for your purposes. I think. @henryiii for visibility.

[mattip]

Blehh. I tried to make the CI runs as compatible as I could. I don't know what is different. Maybe because there are some transient dependencies that are different, like in #5568?

I will drop PyPy3.8, PyPY3.9 in a commit, once I can figure out why the pypy/binary-tests CI is passing while this one fails.

[rwgk]

Blehh. I tried to make the CI runs as compatible as I could. I don't know what is different. Maybe because there are some transient dependencies that are different, like in #5568?

I will drop PyPy3.8, PyPY3.9 in a commit, once I can figure out why the pypy/binary-tests CI is passing while this one fails.

Off the top of my head, I cannot think of anything. We don't do anything special, beyond what's done from cmake, and what you see in our ci.yml.

[rwgk]

I forgot to mention, test_exceptions.py::test_cross_module_exception_translator has been a bit of a troublemaker, see e.g.

• [master] Debugging test_cross_module_exception_translator issue #4054

I never got to the bottom of it.

Maybe just make the strict XFAIL non-strict?

[rwgk]

I'll merge this. We can remove the 3.8, 3.9 PyPy testing separately.