gh-138764: annotationlib - Check if the VALUE_WITH_FAKE_GLOBALS
format is implemented before calling an __annotate__
function with empty fake globals
#138788
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 fixes an issue where user defined
__annotate__
functions that do not support a specific format would be called with fake globals in a way that they couldn't correctly raiseNotImplementedError
.One downside is that some
annotate
functions that may have appeared to 'work' before now correctly fail. It's possible we may want to add some kind of fallback toVALUE
annotations in these cases, but calling with fake globals as it does now would only accidentally succeed depending on exactly how the function performs the comparisons.Current:
With patch:
But change the comparison to check if the format is in a set:
Current:
With patch:
call_annotate_function
should checkVALUE_WITH_FAKE_GLOBALS
is implemented before calling in a namespace with empty fake globals #138764