upstream/ipython Files · IPython/zmq/logtopics.rst

better flush iopub with AsyncResults...

better flush iopub with AsyncResults requesting metadata (e.g. ar.data or ar.stdout) will result in flushing iopub if the outputs are incomplete, so separate wait(0) need not be called. This also applies the workaround discussed in

MinRK - - Load All Authors

File last commit:

r3970:c5a35798


                r8140:c0973b13

Download file

             logtopics.rst
        
                    13 lines
            
             | 454 B
            
                | text/x-rst
            
             |
                RstLexer
            
             / IPython / zmq / logtopics.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        MinRK
    
zmq kernels now started via newapp

              r3970
            
      =======================

      Log Topic Specification

      =======================

      we use pyzmq to broadcast log events over a PUB socket. Engines, Controllers, etc. can all

      broadcast. SUB sockets can be used to view the logs, and ZMQ topics are used to help

      select out what to follow.

      the PUBHandler object that emits the logs can ascribe topics to log messages. The order is:

      <root_topic>.<loglevel>.<subtopic>[.<etc>]

      root_topic is specified as an attribute

	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

MinRK zmq kernels now started via newapp	r3970	=======================
		Log Topic Specification
		=======================

		we use pyzmq to broadcast log events over a PUB socket. Engines, Controllers, etc. can all
		broadcast. SUB sockets can be used to view the logs, and ZMQ topics are used to help
		select out what to follow.

		the PUBHandler object that emits the logs can ascribe topics to log messages. The order is:

		<root_topic>.<loglevel>.<subtopic>[.<etc>]

		root_topic is specified as an attribute