Change string formatting for _successive_halving.py#6375
Merged
not522 merged 2 commits intooptuna:masterfrom Dec 10, 2025
Merged
Change string formatting for _successive_halving.py#6375not522 merged 2 commits intooptuna:masterfrom
_successive_halving.py#6375not522 merged 2 commits intooptuna:masterfrom
Conversation
_successive_halving.py
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.
Motivation
I wanted to change the string formatting according to issue #6305 for compatibility.
Description of the changes
I replaced the use of "{}".format(var) with f-strings as f"{var}" formatting in optuna/pruners/_successive_halving.py