[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] odd/unexpected behavior with Python src blocks

From: Instructor account
Subject: Re: [O] odd/unexpected behavior with Python src blocks
Date: Mon, 29 Sep 2014 11:56:06 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (darwin)

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 <address@hidden> writes:

> 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 matrix-thing [[1.], [1.]] to stdout.  It looks like scipy traps the
> NameErrors and prints them to stderr, but continues its computation
> regardless.
> I’d say babel is performing as desired here, but scipy sadly isn’t
> reporting its errors in the standard way (by a nonzero exit, which I
> think would happen automatically if the NameErrors made it to the top
> level of the stack without being caught).

John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213

reply via email to

[Prev in Thread] Current Thread [Next in Thread]