Closed Evidlo closed 5 years ago
No, not in a general sense. Pyro only exposes objects via autoproxying if these objects are Pyro objects. So you'll have to do a little manual work (registering them with the daemon) before returning them. See the 'autoproxy' example and the documentation of this feature. Main reason is security and the principle to keep the remotely exposed interface explicit.
I'm trying to use PyKeePass remotely to keep a password database open in a background process for a few minutes.
Here are my server and client:
Under the hood,
kp.entries
builds a list of Entry, Group, or Attachment objects.However, I get
TypeError: don't know how to serialize class <class 'lxml.etree._Element'>
because Pyro tries to serialize these objects which contain some lxml_Element
and_ElementTree
objects.In general, is there a way to tell Pyro5 to automatically pass objects of a certain type as remote objects rather than building adapters around every function in PyKeePass?