notebook/IPython
Jason Grout e1a6dbd4be 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.
2015-03-03 16:01:23 +00:00
..
html Handle kernel messages synchronously 2015-03-03 16:01:23 +00:00
nbconvert/exporters
qt/console/tests
testing support case where no server is started 2015-02-07 18:58:39 -05:00
utils preserve umask in atomic_writing 2015-01-14 16:39:52 -08:00