{{ message }}
Select correct method to invoke when keyword arguments are used#1242
Merged
filmor merged 1 commit intopythonnet:masterfrom Oct 1, 2020
Merged
Select correct method to invoke when keyword arguments are used#1242filmor merged 1 commit intopythonnet:masterfrom
filmor merged 1 commit intopythonnet:masterfrom
Conversation
If there were two methods with the same name, but with different arity, `Foo(a)` and `Foo(a,b)`, and the latter was called with a keyword argument `some.Foo(0, b=1)`, `Foo(0)` would be called instead of `Foo(0,1)`. Fixes pythonnet#1235.
filmor
reviewed
Oct 1, 2020
filmor
approved these changes
Oct 1, 2020
Member
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
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.
What does this implement/fix? Explain your changes.
If there were two methods with the same name, but with different arity,
Foo(a)andFoo(a,b), and the latter was called with a keywordargument
some.Foo(0, b=1),Foo(0)would be called instead ofFoo(0,1).Does this close any currently open issues?
Fixes #1235.
Checklist
Check all those that are applicable and complete.
AUTHORSCHANGELOG