##// END OF EJS Templates
Backport PR #2102: Fix logging on interactive shell....
Backport PR #2102: Fix logging on interactive shell. Add a missing string format code in init_logs() and move init_logstart() after init_magics(), to fix dependency issues. This is a proposed fix for the case a log file is given in `ipython_config.py`, eg: ```python # Start logging to the given file in append mode. import os from time import strftime f = os.path.join(c.TerminalIPythonApp.ipython_dir, strftime('%Y-%m-%d')+".py") c.TerminalInteractiveShell.logappend = f ``` which completely breaks in current `master` code

File last commit:

r3970:c5a35798
r7990:a4d72683
Show More
logtopics.rst
13 lines | 454 B | text/x-rst | RstLexer
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