Better error printing

[jw3126]

I often get errors that look like this:

There are a couple of things that make this pretty hard to read. The most important one is probably that instead of an actual line break there appears a literal \n.

Could this be improved? And is it hard to do so?

[PallHaraldsson]

I looked a bit into it, and did see this function:

PyCall.jl/src/exception.jl

Line 180 in 8e3abed

function showerror_string(e::T, bt = nothing) where {T}

It's probably not too hard to change this. Still, not sure, it seems you send many lines to Python to evaluate (that's supported), maybe they should be broken up by you (or PyCall.jl) to many evaluations? Maybe as part of some debug mode?

[jw3126]

Not sure, what you mean by sending many lines to python, but I just call a single method of a python object.

[jw3126]

The above error is from tensorflow.keras and it is representative of what errors from keras look like for me.

[PallHaraldsson]

It seems I misread the cause (i.e. you're not using multi-line py""" vs py "), and rereading this looks like some stack-trace. It should be simple to take it from Python (Keras?) and change \n to an actual newline. There might be a side-effect that some replacements are not wanted... so I'm not sure what's best to do.