On Tuesday, December 1, 2015 at 8:05:50 PM UTC-5, Forrest Curo wrote: > > The amount of glue I needed to write was minimal, considering that I > didn't want to have to decide how much of the time a routine would devote > to listening on a port, nor how many messages might be received between > calls, nor how to get a list of these into julia. > > Trying to tell julia how to take someone else's python 'Port' and > 'Message' objects apart in julia, without knowing what julia types to > expect from that was confusing. The notation for calling those objects' > python methods directly from julia had me overwhelmed. If I turned those > methods into python functions, PyCall translated them easily. >
It seems better in the long run just to learn how to use PyCall. I'm not sure what you mean by "taking someone else's objects apart". Usually there are straightforward rules for converting Python code into the corresponding Julia code. In your example, of calling mymod.myf(x) to access x.theirmethod, you could just call x[:theirmethod].
