Open
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
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.
Hello!
While reading the code and running some tests, I noticed a small detail that could cause unexpected behavior when the input list is not ordered. The
itertools.groupby()function assumes the data is already sorted by the key (docs), but in_group_by_match_indexthis was not guaranteed.So I added a
sorted()call before thegroupby()to make the behavior safe and consistent, regardless of the input order.Interestingly, the rest of the codebase already follows this same pattern:
sorted()beforegroupby()I also added a small test that explicitly checks the behavior with unsorted input data, just to make sure this case is always covered.
Thank youfor the project!
I hope this improvement is helpful.