Use TYPE_CHECKING in pruners/_threshold.py#6487
Merged
not522 merged 1 commit intooptuna:masterfrom Mar 2, 2026
Merged
Conversation
TYPE_CHECKING in pruners/_threshold.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
Refs #6029
Description of the changes
Move
import optunainto aTYPE_CHECKINGblock inoptuna/pruners/_threshold.py, since it is only used in type annotations and the file already hasfrom __future__ import annotations. Replaced string-quoted annotations with direct references.Verified with
ruff check optuna/pruners/_threshold.py --select TCH.