-
Notifications
You must be signed in to change notification settings - Fork 747
An overload with a parameter of type object
is not used
#811
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
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Jan 28, 2019
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Feb 11, 2019
…instead of failing This enables overload resolution with object parameters to behave the same way PyObject parameters behave - e.g. allow any Python object to be passed as PyObject as fallback. Resolves pythonnet#811
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Feb 11, 2019
…calling C# from Python Related: pythonnet#811, pythonnet#265, pythonnet#782
Yes, it's a possibility to do that. The issue at hand is probably, that Python objects do not derive from |
I'll need to look into this, could you make a PR from this commit? |
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Apr 24, 2019
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Apr 24, 2019
…instead of failing This enables overload resolution with object parameters to behave the same way PyObject parameters behave - e.g. allow any Python object to be passed as PyObject as fallback. Resolves pythonnet#811
4 tasks
4 tasks
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Jun 26, 2019
…calling C# from Python Related: pythonnet#811, pythonnet#265, pythonnet#782
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Oct 21, 2019
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Oct 21, 2019
…instead of failing This enables overload resolution with object parameters to behave the same way PyObject parameters behave - e.g. allow any Python object to be passed as PyObject as fallback. Resolves pythonnet#811
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Feb 27, 2020
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Feb 27, 2020
…instead of failing This enables overload resolution with object parameters to behave the same way PyObject parameters behave - e.g. allow any Python object to be passed as PyObject as fallback. Resolves pythonnet#811
filmor
pushed a commit
that referenced
this issue
Mar 3, 2020
…m Python (#889) * added a regression test for #881 * when converting to object, wrap values of unknown type into PyObject instead of failing This enables overload resolution with object parameters to behave the same way PyObject parameters behave - e.g. allow any Python object to be passed as PyObject as fallback. Resolves #811 * fixed ObjectField conversion test * fixed test_object_indexer to pass on custom class key * use object() instance in OverloadResolution_UnknownToObject test
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
May 14, 2020
…tails Similar to pythonnet#900, but for constructors (reuses the same code) Related issues: pythonnet#811, pythonnet#265, pythonnet#1116
filmor
pushed a commit
that referenced
this issue
May 14, 2020
AlexCatarino
pushed a commit
to QuantConnect/pythonnet
that referenced
this issue
Jun 18, 2020
…m Python (pythonnet#853) * added a regression test for pythonnet#881 pythonnet#811 * when converting to object, wrap values of unknown type into PyObject instead of failing This enables overload resolution with object parameters to behave the same way PyObject parameters behave - e.g. allow any Python object to be passed as PyObject as fallback. Resolves pythonnet#811
AlexCatarino
pushed a commit
to QuantConnect/pythonnet
that referenced
this issue
Jun 18, 2020
…pythonnet#900) * generate more useful message, when a .NET overload can't be found, that matches Python parameter types * provide detailed error message, when an overload can't be found when calling C# from Python Related: pythonnet#811, pythonnet#265, pythonnet#782
AlexCatarino
pushed a commit
to QuantConnect/pythonnet
that referenced
this issue
Jun 29, 2020
…m Python (pythonnet#889) * added a regression test for pythonnet#881 * when converting to object, wrap values of unknown type into PyObject instead of failing This enables overload resolution with object parameters to behave the same way PyObject parameters behave - e.g. allow any Python object to be passed as PyObject as fallback. Resolves pythonnet#811 * fixed ObjectField conversion test * fixed test_object_indexer to pass on custom class key * use object() instance in OverloadResolution_UnknownToObject test
AlexCatarino
pushed a commit
to QuantConnect/pythonnet
that referenced
this issue
Jun 29, 2020
…tails (pythonnet#1143) Similar to pythonnet#900, but for constructors (reuses the same code) Related issues: pythonnet#811, pythonnet#265, pythonnet#1116
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Details
I am trying to get Python call my C# method, which has a parameter of type
object
with an instance of Python'sKeyError
.Where
ObjOrClass
definition is:public void ObjOrClass(object _) => this.Value = Object;
. The actual function body here is not important.Possibly related:
#265
#782
Thoughs
IMHO, Python.NET should create a
PyObject
and pass it here.The text was updated successfully, but these errors were encountered: