##// 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:

r13582:b21d447e
r18454:d2c994e5
Show More
_dummy.py
29 lines | 578 B | text/x-python | PythonLexer
#-----------------------------------------------------------------------------
# Copyright (C) 2013 Min RK
#
# Distributed under the terms of the 2-clause BSD License.
#-----------------------------------------------------------------------------
from contextlib import contextmanager
def beginActivityWithOptions(options, reason=""):
return
def endActivity(activity):
return
def nope():
return
def nap():
return
@contextmanager
def nope_scope(
options=0,
reason="Because Reasons"
):
yield
def napping_allowed():
return True