-
Notifications
You must be signed in to change notification settings - Fork 561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bogus error message on timeout with --execute #74
Comments
I agree, that should have a more useful error message. Do you want to make a PR? |
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. |
You can install it from a clone with I expect you'll need to catch the |
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 |
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. |
When a cell times out in nbconvert with
--execute
flag the traceback shows this traceback:I believe the raised error message here should be more informative (I didn't realize there was a timeout at all).
Details: tested on IPython 3.2.1, with a notebook containing a single cell
Using the command
ipython nbconvert --to notebook --execute test_notebook.ipynb
.The text was updated successfully, but these errors were encountered: