is important for the way you write your log messages you have to write sentences that can be understood without knowing their context (which is a good idea anyway). only log entries at levels CRITICAL, ERROR, and WARNING are shown.This also means that the logging configuration is bog standard. As a result, you can just grab a Python tutorial, apply it to Blender, and get the results you’d expect. We keep Blender’s Python as default and standard as possible. Only use those sparingly, for those things you intend to be seen by end users. Be careful which one you choose, though: errors and warnings are shown on the console by default, so they can be seen by anyone. To log something, use one of the error, warning, info, or debug functions (for details, see the API documentation). Loggers use a hierarchy of dotted names, so if you want to create a sub-logger (for example to use in an operator), you can use log = logging.getLogger(_name_ + '.my_sublogger'). The general approach to logging is to use the module’s name as the logger name, so your module can have this at the top: import logging To familiarize yourself with Python’s logging module itself, we can recommend the Logging HOWTO by Vinay Sajip. Python’s standard library with a very flexible and extendable logging module. When things take an unexpected turn, which they always do, it is great to know what is going on behind all the nice GUIs and user-friendly operators. In this article we take a look at using logging inside Blender.

Blender print