-
-
Notifications
You must be signed in to change notification settings - Fork 230
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
Issue/#159 - consistent names for loggers #180
Conversation
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.
I would prefer a more generic and fail-safe solution; e.g., by using CLASS.__module__+"."+CLASS.__name__
You don't need to worry about minimal coverage reduction. And I agree with Marius' suggestion for class naming. |
I can do that, but logger-names will not be as nice for the eyes, e.g. |
Changed logger-names and removed most trailing white-spaces while at it.
Coverage decreased because a line duplicate is removed in runhistory2epm... not sure what to do about it.