Use __future__.annotations in matplotlib/_intermediate_values#6425
Merged
not522 merged 1 commit intooptuna:masterfrom Jan 27, 2026
Merged
Conversation
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
Issue #4508 tracks the ongoing effort to use postponed evaluation of type annotations across the Optuna codebase.
The matplotlib intermediate values visualization currently uses quoted type annotations for Axes due to conditional imports. Using from future import annotations allows these annotations to be evaluated lazily, improving readability and consistency with other visualization modules.
Description of the changes
Fixes #4508