Make all type annotations lazy #386
Merged
Conversation
This file contains 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
|
CI is just being a drama queen again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PEP 563 introduced postponed evaluation of type annotations. It makes importing modules faster and allows to use the latest Python features in older Python releases and to use forward references and type-checking-only objects without quoting annotations. In other words, a lot of cool stuff. The feature can be activated since Python 3.7 by adding in the file
from __future__ import annotations. The feature was supposed to be the default behavior since Python 3.10 or so, but was postponed indefinitely because of some corner cases when it doesn't work well (runtime type annotation evaluation for closures).