-
Notifications
You must be signed in to change notification settings - Fork 751
Selecting overloaded methods with unsigned integer argument fails #283
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can't you convert to .NET type(s) before passing in? There is no built-in On Fri, Nov 4, 2016, 8:05 AM makalu79 notifications@github.com wrote:
|
Yes, that would be possible. But when using "3rd party" assembly, that would mean to write wrappers around every method including range checking. Of course, if the .NET method has overloaded signature which just differs by an argument being either unsigned or signet integer, we're out of luck! But the strage thing is, the exact same code worked in pythonnet 2.0.0. I tried to attach a patch file for pythonnet 2.1.0 version of runtime/converter.cs which solved the problem for me, didn't work, so pardon me for pasting it into the comments below.
|
Uh oh!
There was an error while loading. Please reload this page.
When trying to invoke a .NET method with a unsigned integer argument, it fails with "No method matches given arguments", if there is another method signature with the same name. To reproduce, use the class:
Then called from python with:
line 2 works fine, but lines 3 and 4 fail with TypeError: No method matches given arguments (using 2.1.0)
The text was updated successfully, but these errors were encountered: