Since it should be possible to call any Python module, I'm not sure there is much benefit to be able to call Octave directly. Except maybe:
There is a way to call MATLAB directly (and back) that doesn't involve Python (I think). I haven't looked too much into it as I do not have to do this personally (but a friend could use this). Those wrappers are probably specific to call MATLAB. How hard would it be to make them generic? Or should there be a third module for that (an abstract interface)? [And I'm thinking along similar lines for my Decimal package that uses Python and then another implementation that wraps C.] It seems it would be unfortunate if the MATLAB wrapper's interface looks different from the oct2py interface - is that inevitable? People who already know that interface from Python expect that one (or do we not need that compatibility?)? In Julia, things could be slightly different, but in the end, you just want to call some MATLAB/Octave functions, right? Couldn't most stuff at least be the same? -- Palli. On Friday, February 6, 2015 at 9:40:17 PM UTC, Steven G. Johnson wrote: > > > > On Friday, February 6, 2015 at 2:03:23 PM UTC-5, astromono wrote: >> >> I am getting to julia in recent months. I have hundreds >> (thousands, perhaps) of functions and scrips in octave (many years >> working with matlab/octave). I'm linux user (LMDE). >> The fact is that from python I use oct2py module to run octave functions >> with reasonably good results. >> But in julia, using PyCall, this fails. >> To begin "@pyimport oct2py.octave as oc" leaves locked the command until >> you cancel it: >> >> julia>pyimport oct2py.octave as oc >> > > Can you file a PyCall issue? I'm not sure what is going on, as I don't > have the oct2py module installed at the moment and can't try it out > quickly, but it should be possible to get any Python module working from > Julia. >
