- Notifications
You must be signed in to change notification settings - Fork756
Temporary fix method binder for out parameters#1672
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
@eirannejad, please add a test or two to cover the new code. |
Uh oh!
There was an error while loading.Please reload this page.
existing tests are passing bogus values to force matching the method signaturethese tests should pass with the recent method binder fix, without passing the bogus values
lostmsu left a comment• edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Please, keep old test scenarios unless they are actually not supported anymore.
Uh oh!
There was an error while loading.Please reload this page.
(I'm a bit new to Github review/request change process. I apologize in advance if I clicked too many things) |
@eirannejad We'd need you to sign the .NET Foundation CLA:https://cla.dotnetfoundation.org/pythonnet/pythonnet @lostmsu Please have an eye on this for first-time contributors until the CLA bot is fixed. |
Uh oh!
There was an error while loading.Please reload this page.
What does this implement/fix? Explain your changes.
Current method binder code needs cleanup. There is an active issue with pythonnet failing to find the appropriate overload when the method signature includes
out
parameters e.g.SomeMethod(int a, out int b)
. Current workaround is to call the method by providing bogus value for theout
parameter e.g.SomeMethod(1, 0)
instead ofSomeMethod(1)
This PR pushes a temporary fix for this problem until the binder code is cleaned up. The change is intentionally minimal.
Does this close any currently open issues?
Not sure. Can not find anything related to this by looking at open issue titles
Any other comments?
No
Checklist
AUTHORS
CHANGELOG