##// 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 / parallel / tests
__init__.py Loading ...
clienttest.py Loading ...
test_asyncresult.py Loading ...
test_client.py Loading ...
test_db.py Loading ...
test_dependency.py Loading ...
test_launcher.py Loading ...
test_lbview.py Loading ...
test_magics.py Loading ...
test_mongodb.py Loading ...
test_view.py Loading ...