don't force instantiation of contents manager by default...

don't force instantiation of contents manager by default this is never used and never needed, and results in the instantiation of a contents manager that is immediately discarded.

MinRK - - Load All Authors

File last commit:

r9372:37f32253


                r20491:86a2891d

Download file

             logtopics.rst
        
                    13 lines
            
             | 454 B
            
                | text/x-rst
            
             |
                RstLexer

/ IPython / kernel / zmq / logtopics.rst

History | Annotation | Raw |Copy content |Copy permalink

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