upgrade pyupgrade to start using 3.10+#604
Open
Vizonex wants to merge 7 commits into
Open
Conversation
for more information, see https://pre-commit.ci
…to pyupgrade-310
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
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.
What do these changes do?
This Pull request bumps pyupgrade to use 3.10+ code instead of 3.8. The PR Aims to have pre-commit run and change code as well as aid in helping to maintain readability with the code.
from __future__ import annotationssystem.Are there changes in behavior for the user?
Unions and Option typehints should be replaced and items labeled as deprecated in the typing module should be properly moved to the
collections.abcmodule.Related issue number
Checklist