Python's logging facility comes with several levels of severity:
- CRITICAL
- ERROR
- WARNING*
- INFO
- DEBUG
- NOTSET
*The root logger defaults to WARNING.
How does one deal with regular messages in this setup?
With "regular messages" I mean those that are not warnings but should always be shown to the user.
An example could be:
Loop over a list of files and apply an accumulating operation to them. A "regular message" could be "currently working on {filename}". The INFO level might hold the status of individual sub-steps of the file treatment that the user may not be interested in knowing most of the time. On the WARNING level could be potential problems like two files containing differing entries for the same key.
I think that I want a level between WARNING and INFO, which might be called NOTICE, NOTE, REGULAR or similar. This level would be my default instead of WARNING. Why does logging not provide such a level?
I understand that I can add such a level fairly easily but the logging manual strongly argues against custom levels. Thus, I assume there must be a canonical way of logging messages like the above ...
EDIT: Just to clarify regarding the vote to close for being "opinion-based": I would like to know how logging is supposed to be used sticking to the given set of levels and conventions. Thus, I would think that the correct answer is not necessarily an opinion but should be the best practice of using this module.
The manual states "Defining your own levels is possible, but should not be necessary, as the existing levels have been chosen on the basis of practical experience". In my example above, I seem to be lacking one level: either "regular messages" or -- if I switch to INFO meaning "regular messages" -- something like "verbose info" for the user.
INFOlevel, while the level that "might hold the status of individual sub-steps of the file treatment that the user may not be interested in knowing most of the time" is intuitively the DEBUG level. Why does logging not provide such a level? 1. Because there's no strict convention on what the logging levels are and it would be impossible to satisfy everyone's needs. 2. In your case, the defined levels are more than enough IMO.loggingso strict about it's own convention? I know the answer is: in order to have compatibility between modules written by different people. Anyway, if I follow your suggestion of using INFO for user-visible messages and DEBUG for the developer, I am now lacking something between those two levels: "verbose info" for the user. Finally, if that was the intended way, why isn't INFO the default level?