This supersedes PR #4268.
Run the tests with '--subproc-streams show' to show output from
subprocesses (kernels, IPython.parallel components) in the terminal, or
with '--subproc-streams discard' to send it to /dev/null. By default (or
with '--subproc-streams capture') the output is piped, captured and
displayed only when tests fail. But in some situations, a test fails
because of an error which actually occurred earlier, so you have to see
all the output.
Stop bundling the numpydoc Sphinx extension
numpydoc is now a separately installable package, so we can express a dependency for the 'doc' install option, rather than bundling it. This gets us bugfixes that our copy was lacking - one of which was causing a problem for the ShiningPanda docs job.
numpydoc is now a separately installable package, so we can express a
dependency for the 'doc' install option, rather than bundling it. This
gets us bugfixes that our copy was lacking - one of which was causing a
problem for the ShiningPanda docs job.
Fixing various output related things:
JavaScript output no longer requires calling container.show()
Added output_javascript CSS class that has zero height when empty.
JavaScript error messages are properly indented with the prompt area.
This was inspired by PR #4105.
* JavaScript output no longer requires calling container.show()
* Added output_javascript CSS class that has zero height when
empty.
* JavaScript error messages are properly indented with the prompt
area.
This is a reponse to the problem of having really long lines in
Markdown cells, which makes the content difficult to read. Users
want wide code cells, so we don't want to narrow everything. The
solution here is to give a prompt area to the heading/md cells
to narrow their content area slightly. The only problem is that
this makes it more difficult to distinguish between output
and md content that follows that output. The solve this, we are
adding a narrow line between output and following md.
Don't check for wx in the test suite.
An interaction between wx and threads was blocking certain Unix signals,
causing an unrelated test to fail for me.
We were only checking for wx to exclude the inputhookwx module from the
test run. It contains no tests anyway, so we may as well just exclude it
in all cases.
An interaction between wx and threads was blocking certain Unix signals,
causing an unrelated test to fail for me.
We were only checking for wx to exclude the inputhookwx module from the
test run. It contains no tests anyway, so we may as well just exclude it
in all cases.
