##// END OF EJS Templates
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.

File last commit:

r17765:7c1173bb
r18454:d2c994e5
Show More
__init__.py
15 lines | 334 B | text/x-python | PythonLexer
try:
from appnope import *
except ImportError:
__version__ = '0.0.5'
import sys
import platform
from distutils.version import LooseVersion as V
if sys.platform != "darwin" or V(platform.mac_ver()[0]) < V("10.9"):
from ._dummy import *
else:
from ._nope import *
del sys, platform, V