-
Notifications
You must be signed in to change notification settings - Fork 1
GEOPY-2420: change get_logger function to define setLevel #151
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
Open
MatthieuCMira
wants to merge
5
commits into
develop
Choose a base branch
from
GEOPY-2420
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
644b7bb
update get_logger to accept set_level as a string.
MatthieuCMira 287c50d
remove catching logger error, will raises a clear enough error anyway
MatthieuCMira 0c93d04
Merge branch 'develop' into GEOPY-2420
MatthieuCMira 1f68d31
small change
MatthieuCMira 797d413
Merge remote-tracking branch 'origin/GEOPY-2420' into GEOPY-2420
MatthieuCMira File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,72 @@ | ||
| # ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | ||
| # Copyright (c) 2025 Mira Geoscience Ltd. ' | ||
| # ' | ||
| # This file is part of geoapps-utils package. ' | ||
| # ' | ||
| # geoapps-utils is distributed under the terms and conditions of the MIT License ' | ||
| # (see LICENSE file at the root of this source code package). ' | ||
| # ' | ||
| # ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | ||
| from __future__ import annotations | ||
|
|
||
| import logging | ||
|
|
||
| import pytest | ||
|
|
||
| from geoapps_utils.utils.logger import get_logger | ||
|
|
||
|
|
||
| def test_logger_warning(caplog): | ||
| """ | ||
| Test that the logger is set up correctly. | ||
| """ | ||
| # test with everything | ||
| logger = get_logger( | ||
| "my-app", | ||
| timestamp=True, | ||
| level_name=True, | ||
| propagate=True, # will be set to false because level | ||
| add_name=True, | ||
| level="warning", | ||
| ) | ||
|
|
||
| with caplog.at_level(logging.WARNING): | ||
| logger.warning("Test log message") | ||
|
|
||
| assert "Test log message" in caplog.text | ||
| assert "my-app" in caplog.text | ||
| assert "WARNING" in caplog.text | ||
|
|
||
|
|
||
| def test_logger_info(caplog): | ||
| # test with nothing (expect propagate) | ||
| logger_2 = get_logger( | ||
| timestamp=False, | ||
| level_name=False, | ||
| propagate=True, | ||
| add_name=False, | ||
| ) | ||
|
|
||
| with caplog.at_level(logging.INFO): | ||
| logger_2.info("Test log message") | ||
|
|
||
| assert "Test log message" in caplog.text | ||
| assert caplog.records[0].levelname == "INFO" | ||
| assert caplog.records[0].name == "root" | ||
|
|
||
|
|
||
| def test_logger_no_propagate(caplog): | ||
| # test with propagate false | ||
| logger_3 = get_logger( | ||
| "my-app", timestamp=False, level_name=False, propagate=False, add_name=False | ||
| ) | ||
|
|
||
| with caplog.at_level(logging.INFO): | ||
| logger_3.info("Test log message") | ||
|
|
||
| assert caplog.text == "" | ||
|
|
||
|
|
||
| def test_logger_level_errors(): | ||
| with pytest.raises(TypeError, match="Level must be a string or LoggerLevel"): | ||
| get_logger(level=5) # type: ignore |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Even wonder if we should not simplify and just expect a
Literal[logging.WARNING, logging.INFO...]. It's not that much work on the other side to just import logging if you want to make specific cases.Uh oh!
There was an error while loading. Please reload this page.
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.
Because it's something we are using everywhere, we can have the luxury to create our loggers from a string in this function. That's for us.
It's not a lot of work, but quite convenient to just create a logger this way!