[3.13] gh-126986: Stop Using _PyInterpreterState_FailIfNotRunning()#127112
Uh oh!
There was an error while loading. Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
…h-126988) We replace it with _PyErr_SetInterpreterAlreadyRunning().
zware approved these changes Nov 21, 2024
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a pseudo-backport of d6b3e78 (gh-126988). In that change for 3.14+, we dropped
_PyInterpreterState_FailIfNotRunning()and added_PyErr_SetInterpreterAlreadyRunning(). Here, we replace usage of_PyInterpreterState_FailIfNotRunning()with the inlined equivalent of_PyErr_SetInterpreterAlreadyRunning(), without adding that function. That way we avoid changing the 3.13 ABI.