Bogus error message on timeout with --execute about nbconvert HOT 5 CLOSED

I agree, that should have a more useful error message. Do you want to make a PR?

from nbconvert.

Depends: at this point I don't understand neither how to install current nbconvert nor the testing policy. If it's just editing the error type&message, then sure.

from nbconvert.

You can install it from a clone with pip install --pre -e . (--pre because it will pull in a pre-release version of IPython). You can run the tests with nosetests.

I expect you'll need to catch the Empty error and raise a new exception in its place.

from nbconvert.

OK, after checking the source I saw there is already a description of what happens, and moreover it is very decent in nbconvert 4.0 compared to ipython 3. The only problem in my view is that it is buried by the traceback (the one I've copied in the original message). Would re-raising CellExecutionError("Cell execution timed out, see log for details.") instead of Empty be a reasonable way to point to the log?

from nbconvert.

I think I'd leave CellExecutionError for actual errors in the user code. I'd use TimeoutError in Python 3, and maybe RuntimeError in Python 2. The message you suggest looks fine, though.

from nbconvert.