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
docs	Merge pull request #7878 from minrk/nbconvert-downgrade	2015-02-27 10:06:09 -08:00
examples	Update Widget Events.ipynb	2015-03-02 11:27:10 +00:00
git-hooks	Git hooks need to use invoke, not fab	2014-12-10 10:35:00 -08:00
IPython	Handle kernel messages synchronously	2015-03-03 16:01:23 +00:00
tools/tests	add kernel metadata to example notebooks	2015-01-30 13:57:37 -08:00
.gitignore	[issue547] add emacs tmp files and .coverage files to gitignore	2014-11-07 23:09:44 +00:00
.mailmap	update mailmap	2015-01-30 13:57:36 -08:00
Dockerfile	Bump less to @<3.0 so setup.py css works	2015-01-21 22:08:39 -05:00
setup.py	bump pyzmq version dependency to 13	2015-02-05 14:16:48 -08:00
setupbase.py	Merge pull request #7632 from minrk/terminado-dep	2015-02-03 14:28:45 -08:00