juliainterop / octcall.jl Goto Github PK

For Oct2Py at least I got "Session died" (for inv function) and tracked it down to needing:

ENV["OPENBLAS_NUM_THREADS"]="1"

https://github.com/xianyi/OpenBLAS/wiki/faq#multi-threaded

OpenBLAS is ok with threading, but Octave doesn't support the combination, it seems, at least I fixed this way. This needs probably not be reported at Oct2Py, as I think Python doesn't enable threading by default, but Julia does, so for the combination of the three languages is a problem, or I assume would be also for you, this package.

and if, then latest addition here, from 6 days ago:
blink1073/oct2py@8970a66

I'm not sure this applies to Julia, as prety standard to return many there (and I thought in Python?), and in MATLAB:

https://stackoverflow.com/questions/43394393/oct2py-only-returning-the-first-output-argument

Removed inferred nout for Octave function calls; it must be explicitly given if not 1. The old behavior was too surprising and relied on internal logic of the CPython interpreter.

I'm just filing so I do not forget, maybe this is not needed, but if a good idea, then also at MATLAB.jl?