Skip to content

Conversation

@yanoom
Copy link
Contributor

@yanoom yanoom commented Sep 1, 2020

This allows calls to logging.<log_level> to be printed in console, even after Pyctuator's initialization

Copy link
Member

@michaelyaakoby michaelyaakoby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add some more info in the commit comment?
Maybe refer to the issue (by including "#31" in the comment).
Maybe even add a short explanation of the problem.

@yanoom
Copy link
Contributor Author

yanoom commented Sep 2, 2020

Validated fixes are working on all example apps

@MatanRubin
Copy link
Member

I agree with @michaelyaakoby regarding the commit message. Consider using the form of "Before this change, (describe previous behavior here). Now, (describe new behavior here)"

@yanoom yanoom force-pushed the yanay-fix-issue-31-app-logging-conf branch from 3f2e65c to a889949 Compare September 2, 2020 12:35
This allows calls to `logging.<log_level>` to be printed in console, even after Pyctuator's initialization.
Before this change, application needed to call `logging.basicConfig` or
`logging.<any log level>` before initiating Pyctuator (otherwise
Pyctuator has the only handler in logging module, and app prints do not
appear in console).
Fixes #31
@yanoom yanoom force-pushed the yanay-fix-issue-31-app-logging-conf branch from a889949 to b3ef885 Compare September 2, 2020 12:41
@michaelyaakoby michaelyaakoby merged commit 69b30f7 into master Sep 2, 2020
@michaelyaakoby michaelyaakoby deleted the yanay-fix-issue-31-app-logging-conf branch September 2, 2020 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Flask implementation - Pyctuator messes with app logging conf

4 participants