New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DM-31103: Add some python logging compatibility features #56
Conversation
This is the preferred way to create a LogRecord since it allows registered record factories to augment the record in a consistent way.
These three convenience methods are designed to work without a logger but they weren't returning the answer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. My worry is that when we start substituting lsst.log
with logging
there may be cases that pass lsst.log
logging level numbers to logging
methods, would be interesting to find Level 10000
in the logs then.
They are hardly used anywhere (about 15 occurrences in the entire code base).
The kwargs only come via infof-style logging and (1) those are assumed to be formatted into the message ahead of time and (2) are deprecated. This will have to be changed if MDC is ever supported.
@timj, K-T just hinted me that I left |
No description provided.