GH-104580: Put eval_breaker back at the start of the interpreter state. #107383
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
markshannon changed the title eval_breaker back at the start of the interpreter state.eval_breaker back at the start of the interpreter state. Member Author
| @pablogsal you moved this last, AFAICT, so would you mind reviewing? |
pablogsal approved these changes Jul 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 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.
Move the
eval_breakerback to the start of interpreter state.People seem to like moving this field, so I've added comments explaining why it should be the first field in the interpreter state.
eval_breakerandkwnameslocal variables from interpreter definition. #104580