[assertpy] Accept extensions with additional parameters #15329
Merged
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
This comment has been minimized.
This comment has been minimized.
Signed-off-by: Emmanuel Ferdman <[email protected]>
emmanuel-ferdman
changed the title
Formatter.converter assignment in subclasses
emmanuel-ferdman
force-pushed
the
stdlib-fix
branch
from
cf8888f to
2f27900
Compare
Contributor
|
According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉 |
Sign up for free
to 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.
PR Summary
The
add_extensionandremove_extensionfunctions only accepted callables with exactly one parameter, but custom assertions can have additional parameters likedef all_match(self, predicate). Changed toCallable[..., AssertionBuilder[Any]]to match the runtime behavior.Fixes #15326 .