You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exceptions in an ipython sphinx directive, something like
.. ipython::
In [0]: throw ValueError()
are not output to the shell when the sphinx build happens, but now are silently ignored, though the traceback is written out to the output in HTML/PDF...:
In [1]: throw ValueError()
File "<ipython-input-1-af7bbb4db1fc>", line 1
throw ValueError()
^
SyntaxError: invalid syntax
If an exception occurs in an imported module, the full traceback is shown in the sphinx build log. It would be better if there was at least a warning in the sphinx build to let you know that there was a problem in the build, otherwise you have to look at each output page to find errors
The text was updated successfully, but these errors were encountered:
ifnotis_okexceptand"Traceback"inprocessed_output:
s="\nException in %s at block ending on line %s\n"% (filename, lineno)
s+="Specify :okexcept: as an option in the ipython:: block to suppress this message\n"sys.stdout.write('\n\n>>>'+ ('-'*73))
sys.stdout.write(s)
sys.stdout.write(processed_output)
sys.stdout.write('<<<'+ ('-'*73) +'\n\n')
Exceptions in an ipython sphinx directive, something like
are not output to the shell when the sphinx build happens, but now are silently ignored, though the traceback is written out to the output in HTML/PDF...:
If an exception occurs in an imported module, the full traceback is shown in the sphinx build log. It would be better if there was at least a warning in the sphinx build to let you know that there was a problem in the build, otherwise you have to look at each output page to find errors
The text was updated successfully, but these errors were encountered: