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
Changes to TLS usage in 3.13 may cause the last error code to be reset when ensuring, checking or releasing the GIL. We need to preserve the value.
PyGILState_Check was already updated, but the other public APIs need the same update. Potentially some of our internal/public ones too. It might just be best to add it to the PyThread_tss_* functions.
Okay, I can confirm that TlsGetValue breaks convention by clearing the last error code on success, as it has no return value that uniquely indicates failure. So we just need to wrap its calls up.
zooba
added a commit
to zooba/cpython
that referenced
this issue
Feb 27, 2024
Bug report
Changes to TLS usage in 3.13 may cause the last error code to be reset when ensuring, checking or releasing the GIL. We need to preserve the value.
PyGILState_Check
was already updated, but the other public APIs need the same update. Potentially some of our internal/public ones too. It might just be best to add it to thePyThread_tss_*
functions.Linked PRs
The text was updated successfully, but these errors were encountered: