[IPython-dev] IPython messaging spec for warnings with traceback

Andrew Gibiansky andrew.gibiansky at gmail.com
Wed Feb 18 02:27:51 EST 2015

IHaskell currently just publishes a display_data message with the error
message, showing it in red for notebook frontends. Is there a downside to
this approach over writing to stderr or sending an error message? Should I
change this to use a more standard mechanism?

-- Andrew

On Tue, Feb 17, 2015 at 3:09 PM, Thomas Kluyver <takowl at gmail.com> wrote:

> On 17 February 2015 at 14:55, Matthias Bussonnier <
> bussonniermatthias at gmail.com> wrote:
>> I guess if we standardize a spec for traceback, it might make sens to
>> reconsider
>> displaying tracebacks in the middle of execution. But if you already have
>> argument
>> for that now, you can expose them.
> There is an 'error' message for displaying errors, which is separate from
> the execution_reply. IIRC, the error message determines what the UI
> actually sees, and the execution_reply may affect the frontend's behaviour
> (it considers that execution to have failed). If I'm right, sending an
> 'error' message for a warning and then sending execute_reply with status OK
> should work correctly.
> We probably don't need to be sending all the error information twice, but
> that's another issue.
> Thomas
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20150217/908b79af/attachment.html>

More information about the IPython-dev mailing list