##// END OF EJS Templates
Backport PR #8829: Qt5 fix...
Backport PR #8829: Qt5 fix Fix for issue #8757. The problem was that IPython.external.qt was moved to qtconsole.qt, but IPython.external.qt_for_kernel was still trying to import IPython.external.qt. Rather than copying the qt.py file back to external, this PR merges the logic back into qt_for_kernel.py. Deferring to qt.py was a bit silly because both qt.py and qt_for_kernel.py do basically the same thing but in slightly different ways. Moreover, the assumption of qt.py was that if the QT_API environment variable is set, it must be in an ETS environment and need to comply by the ETS import logic. This is not valid, as ipython sets the QT_API environment variable to communicate intent as to Qt version, in `IPython/lib/inputhook.py:385` ...

File last commit:

r1334:049617d6
r21823:e0eb38c1
Show More
test_combo.txt
36 lines | 923 B | text/plain | TextLexer
=======================
Combo testing example
=======================
This is a simple example that mixes ipython doctests::
In [1]: import code
In [2]: 2**12
Out[2]: 4096
with command-line example information that does *not* get executed::
$ mpirun -n 4 ipengine --controller-port=10000 --controller-ip=host0
and with literal examples of Python source code::
controller = dict(host='myhost',
engine_port=None, # default is 10105
control_port=None,
)
# keys are hostnames, values are the number of engine on that host
engines = dict(node1=2,
node2=2,
node3=2,
node3=2,
)
# Force failure to detect that this test is being run.
1/0
These source code examples are executed but no output is compared at all. An
error or failure is reported only if an exception is raised.
NOTE: the execution of pure python blocks is not yet working!