You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was a deliberate choice in p2j ("because allowing conversion to Object could cause excessive ambiguity in overload resolution"), but maybe we need to revisit that choice, because it makes it impossible to pass Python objects to methods that take Object-type arguments. Off the top of my head, even I can't come up with a workaround, so what chance does a user have?
This even applies to PyObject.fromJava(Object), and even if we provided a PyObject overload for it, the conversion functions actively try not to expose PyObject proxies within Python, instead returning the original Python object.
The text was updated successfully, but these errors were encountered:
This was a deliberate choice in p2j ("because allowing conversion to Object could cause excessive ambiguity in overload resolution"), but maybe we need to revisit that choice, because it makes it impossible to pass Python objects to methods that take Object-type arguments. Off the top of my head, even I can't come up with a workaround, so what chance does a user have?
This even applies to PyObject.fromJava(Object), and even if we provided a PyObject overload for it, the conversion functions actively try not to expose PyObject proxies within Python, instead returning the original Python object.
The text was updated successfully, but these errors were encountered: