Address These 5 Questions to Understand Python Logging
1. Why Doesn’t It Use the snake_case Naming Convention?

As we all know, the PEP 8 specified how we should name things in Python. In essence, it’s the so-called “snake_case” naming convention. For instance, we have a function that sends a message. The Pythonic name should be send_message . However, some other languages use the camelCase for function names. In that case, the function should be named as sendMessage .

Unlike other modules in the standard library, the logging module doesn’t use snake_case naming. Instead, it follows the camelCase naming convention. The reason is that this module was contributed by the author Vinay Sajip. According to the author, the development of this module was informed by Java’s logging package and Apache’s log4j, both of which use the camelCase naming conventions. The author continued with this convention in this module. The good thing is that although the module doesn’t follow the snake_case naming convention, it has internal consistency due to its use of the camelCase naming convention. So you’ll be less likely to be confused about various names in the module given its consistency.

For interested users, you can refer to this discussion on Stack Overflow regarding this topic.
['Yong Cui']
['Technology', 'Artificial Intelligence', 'Software Development', 'Programming', 'Python']