Move typing-only imports under TYPE_CHECKING in /study/_optimize.py#6280
Merged
nabenabe0928 merged 1 commit intooptuna:masterfrom Sep 17, 2025
Merged
Conversation
nabenabe0928
approved these changes
Sep 17, 2025
Contributor
nabenabe0928
left a comment
There was a problem hiding this comment.
Thank you for the PR, LGTM:)
TYPE_CHECKING in /study/_optimize.py (part of #6029)TYPE_CHECKING in /study/_optimize.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
This PR continues the type-checking improvements tracked in #6029 for
optuna/study/_optimize.py.Changes
Moved type-only imports (
Callable,Iterable,Sequence,Future,FrozenTrial,Any) underTYPE_CHECKING.Notes
Verified locally with
flake8,mypy(module-level), and relevantpytestruns -- no issues observed.