##// END OF EJS Templates
upstream » ipython
RSS

Clone from https://github.com/ipython/ipython.git

Handle some tricky Comm lifecycle issues...
Handle some tricky Comm lifecycle issues * If the comm was a primary comm, but there was an error opening it, _closed was False, which is wrong * If Comm.close() was called, but an error happened, it still appeared to be open This change makes the _closed attribute more conservative. If _closed is False, the comm is definitely open for messages. If _closed is True, we either didn't initialize correctly, or we tried to close at some point.
Jason Grout -
r18454:d2c994e5
Show More
Name Size Modified Last Commit Author
/ IPython / lib
tests
__init__.py Loading ...
backgroundjobs.py Loading ...
clipboard.py Loading ...
deepreload.py Loading ...
demo.py Loading ...
display.py Loading ...
editorhooks.py Loading ...
guisupport.py Loading ...
inputhook.py Loading ...
inputhookglut.py Loading ...
inputhookgtk.py Loading ...
inputhookgtk3.py Loading ...
inputhookpyglet.py Loading ...
inputhookqt4.py Loading ...
inputhookwx.py Loading ...
kernel.py Loading ...
latextools.py Loading ...
pretty.py Loading ...
security.py Loading ...