chore: remove remaining future annotations#2799
Merged
Conversation
Contributor
|
This clearly works - it passes tests, and evidently it's only the iOS code that is using the future import... but I'm thoroughly confused... I know the original PEP 649 definition called for Python 3.10 as the EOL date for |
Contributor
Author
|
It's not needed because the syntax we are using is valid runtime Python now, has been since 3.10. It does affect forward references, but #2798 cleans those up. |
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.
We still have some future annotations left after we moved to 3.11+. Removing them.