Hello,<br><br>I'm testing out the qtconsole in IPython 0.13.1 and ran into an issue. I have a method which returns a Python 3 future after spawning a thread that does some asynchronous operations over the network. Whenever I enable logging in my application (using the standard Python logging module), this background thread is supposed to print to screen some status/info messages as the operation progresses. This works fine in the text console, but it fails in qtconsole with messages like:<br>
<br>ERROR:root:Uncaught exception, closing connection.<br>Traceback (most recent call last):<br> File "/usr/lib64/python3.2/site-packages/zmq/eventloop/zmqstream.py", line 414, in _run_callback<br> callback(*args, **kwargs)<br>
File "/usr/lib64/python3.2/site-packages/IPython/zmq/kernelmanager.py", line 179, in _handle_recv<br> self.call_handlers(self.session.unserialize(smsg))<br> File "/usr/lib64/python3.2/site-packages/IPython/zmq/session.py", line 726, in unserialize<br>
raise ValueError("Invalid Signature: %r"%signature)<br>ValueError: Invalid Signature: b'd6a302ff4e81d62bb5ec4d1e9ed1e340'<br>ERROR:root:Uncaught exception, closing connection.<br>Traceback (most recent call last):<br>
File "/usr/lib64/python3.2/site-packages/zmq/eventloop/zmqstream.py", line 440, in _handle_events<br> self._handle_recv()<br> File "/usr/lib64/python3.2/site-packages/zmq/eventloop/zmqstream.py", line 472, in _handle_recv<br>
self._run_callback(callback, msg)<br> File "/usr/lib64/python3.2/site-packages/zmq/eventloop/zmqstream.py", line 414, in _run_callback<br> callback(*args, **kwargs)<br> File "/usr/lib64/python3.2/site-packages/IPython/zmq/kernelmanager.py", line 179, in _handle_recv<br>
self.call_handlers(self.session.unserialize(smsg))<br> File "/usr/lib64/python3.2/site-packages/IPython/zmq/session.py", line 726, in unserialize<br> raise ValueError("Invalid Signature: %r"%signature)<br>
ValueError: Invalid Signature: b'd6a302ff4e81d62bb5ec4d1e9ed1e340'<br>ERROR:root:Exception in I/O handler for fd <zmq.core.socket.Socket object at 0x57a57a0><br><br>Here I suspect that the invalid signature b'1dc95584133b5e09c5b1c98a3c77af7f' comes from part of the logging output that is supposed to be printed to screen (which is admittedly rather long). Any hints on what might be going on here? I can try to reduce the test case, but before embarking into that I was wondering if someone can give me any pointer :)<br>
<br>Cheers,<br><br> Francesco.<br>