upstream/ipython Files · IPython/lib/tests

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

Name	Size	Modified	Last Commit	Author
/ IPython / lib / tests
__init__.py	Loading ...
test.wav	Loading ...
test_backgroundjobs.py	Loading ...
test_clipboard.py	Loading ...
test_deepreload.py	Loading ...
test_display.py	Loading ...
test_imports.py	Loading ...
test_latextools.py	Loading ...
test_pretty.py	Loading ...
test_security.py	Loading ...

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages