Avoid taking back GIL when the Python runtime is finalizing

[MiguelCompany]

Description

When using gil_scoped_release, care must be taken not to take the GIL when the Python runtime is finalizing.

According to this one can call _Py_IsFinalizing() to check the failure condition and then disarm() the gil_scoped_release object so it does not take the GIL back.

This would fix (in theroy) #1484 but locally it doesn't seem so. Opening in draft nonetheless, in case someone wants to take this as a base for a proper fix.

Is this user-facing behavior change?

Did you use Generative AI?

Additional Information

[skyegalaxy]

Since the function _Py_IsFinalizing was removed in Python 3.13 (in favor of a public method) this might require some forward compatibility hackiness. In situations like this there's usually a way to check the python version, e.g. something like

#if PY_VERSION_HEX < Py_PACK_FULL_VERSION(3, 13)) 
    #define IsFinalizing _Py_IsFinalizing
#else
    #define IsFinalizing Py_IsFinalizing
#endif

[MiguelCompany]

@skyegalaxy Thanks for the review. I applied your suggestion.

Note however that this is still a draft because:

This would fix (in theroy) #1484 but locally it doesn't seem so. Opening in draft nonetheless, in case someone wants to take this as a base for a proper fix.