Use logger.warning instead of optuna_warn for lock-acquisition delay notifications#6400
Merged
y0z merged 3 commits intooptuna:masterfrom Jan 16, 2026
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Motivation
Follow-up to #6361. This message is not something users can fix by changing their code, but it’s still useful to note as an event. Per Python’s logging guide, this should be logged via
logger.warning()rather than raised withwarnings.warn().Description of the changes
warnings.warn()withlogger.warning()for the lock-acquisition delay notification.