-
Notifications
You must be signed in to change notification settings - Fork 13
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
Importing wakeypy nukes logging config #343
Labels
Type: Bug
Something isn't working
Comments
Oh wow that should not happen! It seems that importing wakepy >0.7.2 changes logging level to |
fohrloop
added a commit
that referenced
this issue
Jun 4, 2024
Fixes: #343 Previously, on wakepy 0.8.0 and 0.9.0, importing wakepy would change logging level to WARNING. This was caused by direct call to logging.debug() when registering Method subclasses.
It was due to some part of the code calling |
No problem. Thanks for the great library :-) |
fohrloop
added a commit
that referenced
this issue
Jun 4, 2024
the logging info may have some side effects (it may configure logging, as in #343)
fohrloop
added a commit
that referenced
this issue
Jun 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
wakeypy > 0.7.2 nukes python logging
When run with wakepy < 0.8.0 the program logs "Running in main" as expected. However, for wakepy > 0.7.2 nothing is logged.
I've tested on both Linux and Window with the same results.
The text was updated successfully, but these errors were encountered: