-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Rule proposal: require explicit strict=
argument for itertools.batched
#14387
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
Labels
rule
Implementing or modifying a lint rule
Comments
I'll take this on. |
Thanks for creating the upstream issue. Let's see what the outcome is upstream before adding this rule to avoid recoding in the near future. |
Merged as |
Great. @InSyncWithFoo do you want to update your PR and recode the rule to B911? |
Done, and thanks @tjkuson for the heads-up. |
MichaReiser
added a commit
that referenced
this issue
Dec 10, 2024
…B911`) (#14408) ## Summary Resolves #14387. ## Test Plan `cargo nextest run` and `cargo insta test`. --------- Co-authored-by: Micha Reiser <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of Python 3.13,
itertools.batched
has astrict
parameter that defaults toFalse
. By default, the batches might not be of the same size, which may cause subtle bugs. Whenstrict=True
, it raisesValueError
if the final batch is not the same size as the rest.This seems analogous to the existing rule
B905
which requires an explicitstrict=
parameter forzip
. Hence, I think it makes sense if there is a similar rule foritertools.batched
.I also created an issue
flake8-bugbear
which seems like a natural place for the rule given the similarity toB905
.Searched keywords:
itertools.batched
,itertools
,batched
The text was updated successfully, but these errors were encountered: