[3.14] Parser stack overflow on `musllinux` `x86_64`

[neutrinoceros]

Bug report

Bug description:

When trying to build and test wheels for yt on 3.14.0rc1, we encounter a single error, only on the musllinux image from cibuildwheel, which crashes on import with

MemoryError: Parser stack overflowed - Python source too complex to parse

example logs:
https://github.com/yt-project/yt/actions/runs/16576917774/job/46883376625?pr=5185

To make things worse, this seems to only happen in the context of a pytest session: python -c "import yt" completes without raising.

A minimal reproducer would necessarily still include a significant amount of complexity, so before I try to reduce it, I'd like to ask:
is it expected that the threshold for triggering this exception may depend on the platform and/or the exact Python version ? is it expected that the threshold may be lower in Python 3.14 than it was in 3.13 ?

CPython versions tested on:

3.14

Operating systems tested on:

Linux

[StanFromIreland]

this seems to only happen in the context of a pytest session: python -c "import yt"

This may mean this is an issue with pytest, it is difficult to deduce without a specific minimal reproducer.

[kumaraditya303]

This seems the same issue as #131338, can you check if the fix at #137175 fixes this?

[neutrinoceros]

Thanks for pointing this out !
it might take some time before I can confirm the fix works for us, but it looks very promising. I'll do my best to actually run the check before 3.14.0rc2 . Does anyone mind if we keep this issue open until then ?

[kumaraditya303]

it might take some time before I can confirm the fix works for us, but it looks very promising. I'll do my best to actually run the check before 3.14.0rc2 . Does anyone mind if we keep this issue open until then ?

The fix is currently scheduled for inclusion in 3.14.0 but RM can include it in 3.14.rc2 as it affects yt and scipy on 3.14, leaving it for @hugovk to decide.

[neutrinoceros]

I've been trying to reproduce the crash with docker (using the same image cibuildwheel runs), but so far I haven't been sucessful: the test session completes without error, so I'm not yet ready to try out the patch, as I except no difference. I'll try to think of a more faithful approach if I can.