Replace more .format() calls with f-strings#6349
Merged
c-bata merged 3 commits intooptuna:masterfrom Nov 21, 2025
Merged
Conversation
Member
|
@varundevr Could you resolve CI errors? |
Contributor
Author
Sure, I have fixed it! |
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
This PR continues the work on issue #6305 by converting remaining
.format()usages into f-strings.This improves readability and keeps the codebase consistent with modern Python practices.
Description of the changes
Replaced a few additional
.format()calls with f-strings in the relevant modules.No functional behavior was changed—only formatting and style improvements were made.