Use TYPE_CHECKING for import in pruners/_base.py#6434
Merged
not522 merged 2 commits intooptuna:masterfrom Feb 13, 2026
Merged
Conversation
Related: optuna#6029 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
pruners/_base.py
pruners/_base.pyTYPE_CHECKING for import in pruners/_base.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.
Summary
Part of #6029
Move
import optunaunderif TYPE_CHECKING:guard inoptuna/pruners/_base.pyto prevent potential circular import issues.Changes
from __future__ import annotationsfor PEP 563 postponed evaluationfrom typing import TYPE_CHECKINGimport optunaunderif TYPE_CHECKING:block