##// END OF EJS Templates
eliminate hardcoded wait, now wait on outputs...
eliminate hardcoded wait, now wait on outputs Note: this test still sometimes fails, though I don't understand why. Increasing the wait time to 30 seconds does not help, which leads me to believe that there's some race condition, or that we're genuinely dropping outputs sometimes (saved notebooks on these timeouts *do* contain an In[] number, but don't have any outputs attached). @ellisonbg and @minrk might now what's going on with that. To run just this test, fire up a notebook server on port 8888 and run: while true; do casperjs test --includes=util.js test_cases/execute_code_cell.js ; done

File last commit:

r9722:7ec1888e
r13277:8cc2a54f
Show More
qt.py
23 lines | 732 B | text/x-python | PythonLexer
""" A Qt API selector that can be used to switch between PyQt and PySide.
This uses the ETS 4.0 selection pattern of:
PySide first, PyQt with API v2. second.
Do not use this if you need PyQt with the old QString/QVariant API.
"""
import os
from IPython.external.qt_loaders import (load_qt, QT_API_PYSIDE,
QT_API_PYQT)
QT_API = os.environ.get('QT_API', None)
if QT_API not in [QT_API_PYSIDE, QT_API_PYQT, None]:
raise RuntimeError("Invalid Qt API %r, valid values are: %r, %r" %
(QT_API, QT_API_PYSIDE, QT_API_PYQT))
if QT_API is None:
api_opts = [QT_API_PYSIDE, QT_API_PYQT]
else:
api_opts = [QT_API]
QtCore, QtGui, QtSvg, QT_API = load_qt(api_opts)