You need datetime.strftime(), this allows you to format the timestamp using all of the directives of C’s strftime(). In your specific case: >>> datetime.now().strftime(‘mylogfile_%H_%M_%d_%m_%Y.log’) ‘mylogfile_08_48_04_02_2012.log’
Don’t use logging.basicConfig, use WatchedFileHandler. Here’s how to use it. import time import logging import logging.handlers def log_setup(): log_handler = logging.handlers.WatchedFileHandler(‘my.log’) formatter = logging.Formatter( ‘%(asctime)s program_name [%(process)d]: %(message)s’, ‘%b %d %H:%M:%S’) formatter.converter = time.gmtime # if you want UTC time log_handler.setFormatter(formatter) logger = logging.getLogger() logger.addHandler(log_handler) logger.setLevel(logging.DEBUG) log_setup() logging.info(‘Hello, World!’) import os os.rename(‘my.log’, ‘my.log-old’) logging.info(‘Hello, New … Read more
Having code like: raise Exception(u’щ’) Caused: File “/usr/lib/python2.7/logging/__init__.py”, line 467, in format s = self._fmt % record.__dict__ UnicodeEncodeError: ‘ascii’ codec can’t encode characters in position 0-3: ordinal not in range(128) This happens because the format string is a byte string, while some of the format string arguments are unicode strings with non-ASCII characters: >>> “%(message)s” … Read more
If you look in the Python sources for logging/__init__.py, you’ll see that basicConfig() sets the handlers on the root logger object by calling addHandler(). If you want to start from scratch, you could remove all existing handlers and then call basicConfig() again. # Example to remove all root logger handlers and reconfigure. (UNTESTED) import logging … Read more
You cannot use new-style formatting when using the logging module; use %s instead of {}. logging.info(‘date=%s’, date) The logging module uses the old-style % operator to format the log string. See the debug method for more detail. If you really want to use str.format() string formatting, consider using custom objects that apply the formatting ‘late’, … Read more
Even though this is a possible duplicate I want to write out a tiny bit of python logging knowledge. DON’T pass loggers around. You can always access any given logger by logging.getLogger(<log name as string>). By default it looks like* flask uses the name you provide to the Flask class. So if your main module … Read more
You could use the logging module: import logging logging.basicConfig(filename=”/tmp/myapp.log”, level=logging.DEBUG, format=”%(asctime)s %(levelname)s %(name)s %(message)s”) logger=logging.getLogger(__name__) try: 1/0 except ZeroDivisionError as err: logger.error(err) Running the script writes in /tmp/myapp.log: % cat /tmp/myapp.log 2010-08-01 17:50:45,960 ERROR __main__ integer division or modulo by zero
Simple solution that works The logging functions will convert the ‘%s’ to string representation (and if the object happens to be a container, then repr() will be used for the contained objects) import logging logging.basicConfig(level=logging.DEBUG, filename=”sample.log”) logging.debug(‘Sample dict log: %s’, {‘name’ : “John”, ‘age’: 10}) How it shows in the log file: DEBUG:root:Sample dict log: … Read more
If you’re using the root logger, for example because you called logging.basicConfig() then you can use import logging logging.root.level For example if logging.DEBUG >= logging.root.level: # Do something
It looks like you’ve set the levels for your handlers, but not your logger. The logger’s level filters every message before it can reach its handlers and the default is WARNING and above (as you can see). Setting the root logger’s level to NOTSET as you have, as well as setting it to DEBUG (or … Read more