Replaced deprecated logger methods 'logger.warn' for 'logger.warning'. #3355
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
This PR replaces the deprecated logger.warn method with logger.warning in 4 instances in a single file.
Why was this change made?
Fixing Warnings: The logger.warn method has been deprecated and triggers warnings during tests. Replacing it with logger.warning resolves these warnings and ensures compatibility with the current version of Python.
Improving Code Clarity: The updated logger.warning method is the correct and preferred approach for logging warnings, which improves the clarity and maintainability of the codebase.
This change should have no functional impact but improves adherence to Python logging best practices.