##// END OF EJS Templates
Handle kernel messages synchronously...
Handle kernel messages synchronously A problem can happen when two messages come in for different comms, where the second depends on the first (for example, the first might be a message setting the state of a widget, and the second triggering a view creation for the widget). Since comm message queues are independent of each other, the second message could be executed before the first message. This exposes a more fundamental assumption users are likely to have that messages from python are processed synchronously. Thanks to @dmadeka for reporting an error that led to discovering this issue.

File last commit:

r16742:9f8aa8d4
r20621:f936f880
Show More
test_app.py
27 lines | 958 B | text/x-python | PythonLexer
"""Test QtConsoleApp"""
#-----------------------------------------------------------------------------
# Copyright (C) 2013 The IPython Development Team
#
# Distributed under the terms of the BSD License. The full license is in
# the file COPYING, distributed as part of this software.
#-----------------------------------------------------------------------------
#-----------------------------------------------------------------------------
# Imports
#-----------------------------------------------------------------------------
import nose.tools as nt
import IPython.testing.tools as tt
from IPython.testing.decorators import skip_if_no_x11
#-----------------------------------------------------------------------------
# Test functions
#-----------------------------------------------------------------------------
@skip_if_no_x11
def test_help_output():
"""ipython qtconsole --help-all works"""
tt.help_all_output_test('qtconsole')