{{ message }}
bpo-43933: Force RETURN_VALUE bytecodes to have line numbers#26054
Merged
markshannon merged 4 commits intoMay 12, 2021
Merged
Conversation
Member
Sorry, something went wrong.
Contributor
|
Thanks @markshannon for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10. |
Sorry, something went wrong.
Contributor
|
Sorry, @markshannon, I could not cleanly backport this to |
Sorry, something went wrong.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.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.
Minimal fix to ensure that all returns have line numbers.
Skipping NEWS as I think PEP 626 is covered well enough already.
I expect this to be a temporary fix for 3.11, as we will implement a proper fix for line number propagation.
https://bugs.python.org/issue43933