You have two options: Open a logfile and replace sys.stdout with it, not a function: log = open(“myprog.log”, “a”) sys.stdout = log >>> print(“Hello”) >>> # nothing is printed because it goes to the log file instead. Replace print with your log function: # If you’re using python 2.x, uncomment the next line #from __future__ … Read more
The problem is that calling getLogger without arguments returns the root logger so when you set the level to logging.DEBUG you are also setting the level for other modules that use that logger. You can solve this by simply not using the root logger. To do this just pass a name as argument, for example … Read more
Have you looked at python docs site section describing Implementing structured logging that explain how python built-in logger can be utilized for structured logging? Below is a simple example as listed on above site . import json import logging class StructuredMessage(object): def __init__(self, message, **kwargs): self.message = message self.kwargs = kwargs def __str__(self): return ‘%s … Read more
Indeed, logging.basicConfig does nothing if a handler has been set up already: This function does nothing if the root logger already has handlers configured, unless the keyword argument force is set to True. You’ll need to either add force=True (requires Python 3.8 or newer), or, alternatively, replace the current handler on the root logger: import … Read more
What Python version? That works for me in 3.4. But note that basicConfig() won’t affect the root handler if it’s already setup: This function does nothing if the root logger already has handlers configured for it. To set the level on root explicitly do logging.getLogger().setLevel(logging.DEBUG). But ensure you’ve called basicConfig() before hand so the root … Read more
Python lets you capture and assign sys.stdout – as mentioned – to do this: import sys old_stdout = sys.stdout log_file = open(“message.log”,”w”) sys.stdout = log_file print “this will be written to message.log” sys.stdout = old_stdout log_file.close()
Python provides 5 logging levels out of the box (in increasing order of severity): DEBUG, INFO, WARNING, ERROR and CRITICAL. The default one is WARNING. The docs says, that Logging messages which are less severe than lvl will be ignored. So if you use .debug with the default settings, you won’t see anything in your … Read more
Call logging.basicConfig(): >>> import logging >>> logging.basicConfig() >>> logger = logging.getLogger(‘logger’) >>> logger.warning(‘The system may break down’) WARNING:logger:The system may break down
Yes, it does flush the output at every call. You can see this in the source code for the StreamHandler: def flush(self): “”” Flushes the stream. “”” self.acquire() try: if self.stream and hasattr(self.stream, “flush”): self.stream.flush() finally: self.release() def emit(self, record): “”” Emit a record. If a formatter is specified, it is used to format the … Read more
When your logger initialized in the beginning of “another module” it links to another logger. Which handle your messages. It can be root logger, or usually I see in Django projects – logger with name ”. Best way here, is overriding your logging config: LOGGING = { ‘version’: 1, ‘disable_existing_loggers’: True, ‘formatters’: { ‘simple’: { … Read more