-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[flake8-bugbear] Mark B905 and B912 fixes as unsafe
#20695
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
Contributor
ntBre
approved these changes
Oct 7, 2025
Contributor
ntBre
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
B905 and B912 strict fixes as unsafeflake8-bugbear] Mark B905 and B912 fixes as unsafe
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.
Resolves #20694
This PR updates the
zip_without_explicit_strictandmap_without_explicit_strictrules so their fixes are always marked unsafe, following Brent's guidance that addingstrict=Falsecan silently preserve buggy behaviour when inputs differ. The fix safety docs now spell out that reasoning, the applicability drops toUnsafe, and the snapshots were refreshed so Ruff clearly warns users before applying the edit.