Set logging level to INFO for management commands#267
Merged
knikolla merged 1 commit intonerc-project:mainfrom Dec 4, 2025
Merged
Set logging level to INFO for management commands#267knikolla merged 1 commit intonerc-project:mainfrom
knikolla merged 1 commit intonerc-project:mainfrom
Conversation
Also replaced deprecated `logger.warn()` with `logger.warning()`
knikolla
approved these changes
Nov 18, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #266. As far as I could tell, there isn't a simple way to systematically set the logging level when running management commands to
INFO. There probably is something I could come up with using Django logging configurations, or by creating a base management command class, but I think a more involved solution can be considered when our commands share more in common.