Switch type comparisons from == to is, and upgrade flake8, in preparation for Python 3.12 #2857
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
Upcoming Python 3.12 (at least in python 3.12-rc1) requires a newer version of flake8 as flake8 6.0.0 gets confused by things happening inside format strings with Python 3.12-rc1. This PR makes that upgrade. Flake8 6.1.0 introduces a new rule to use is-equality, rather than ==-equality, when comparing types, and so this PR fixes violations of that rule too. In theory this shouldn't change behaviour.
khk-globus
approved these changes
Aug 10, 2023
benclifford
changed the title
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.
Upcoming Python 3.12 (at least in python 3.12-rc1) requires a newer version of flake8 as flake8 6.0.0 gets confused by things happening inside format strings with Python 3.12-rc1.
This PR makes that upgrade.
Flake8 6.1.0 introduces a new rule to use is-equality, rather than ==-equality, when comparing types, and so this PR fixes violations of that rule too. In theory this shouldn't change behaviour.
Type of change