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

r13665:bf0f48be
r18454:d2c994e5
Show More
test_python.py
39 lines | 1.3 KiB | text/x-python | PythonLexer
"""Tests for PythonExporter"""
#-----------------------------------------------------------------------------
# Copyright (c) 2013, the IPython Development Team.
#
# Distributed under the terms of the Modified BSD License.
#
# The full license is in the file COPYING.txt, distributed with this software.
#-----------------------------------------------------------------------------
#-----------------------------------------------------------------------------
# Imports
#-----------------------------------------------------------------------------
from .base import ExportersTestsBase
from ..python import PythonExporter
#-----------------------------------------------------------------------------
# Class
#-----------------------------------------------------------------------------
class TestPythonExporter(ExportersTestsBase):
"""Tests for PythonExporter"""
exporter_class = PythonExporter
should_include_raw = ['python']
def test_constructor(self):
"""
Can a PythonExporter be constructed?
"""
PythonExporter()
def test_export(self):
"""
Can a PythonExporter export something?
"""
(output, resources) = PythonExporter().from_filename(self._get_notebook())
assert len(output) > 0