In case anyone else is interested, here is a workaround of sorts to
capture stderr in a python block:
https://github.com/jkitchin/pycse/blob/master/pycse/sandbox.py
You use this module to redefine stdout and stderr. You basically run
python like this:
#+BEGIN_SRC emacs-lisp
(setq org-babel-pyth
Indeed, this passes by org-babel because stderr is not captured, and
scipy does what you suggest. I guess this happens inside compiled
c/Fortran code since there is nothing catching it in the odeint
python function doing that.
Thanks, I will try to bring it up on the scipy list.
Aaron Ecay writ
Hi John,
2014ko irailak 28an, John Kitchin-ek idatzi zuen:
[...]
> I am not sure why this happens, but it seems like incorrect behavior to
> me.
In the first case, python exits with a non-zero exit code, whereas in
the second it exits with a zero code (i.e. successful exit), and prints
the matr
