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
The RPCGenerator in #3 depends on the private API of jsonrpc2-pyclient, as the baseclass is intended to include some message transfer methods, which are incompatible with pyleco.
The text was updated successfully, but these errors were encountered:
The private API is from jsonrpc2pyclient._irpcclient import IRPCClient, which we inherit from.
Maybe useful: In what way are these message transfer methods incompatible?
When the dust has settled, it might be worth it to inquire about this upstream, maybe this points to a design change on their end, or there is a better way to achieve what we need?
The RPCGenerator in #3 depends on the private API of
jsonrpc2-pyclient
, as the baseclass is intended to include some message transfer methods, which are incompatible with pyleco.The text was updated successfully, but these errors were encountered: