Reformat datespan.py to satisfy Black check#85
Open
estebanzimanyi wants to merge 1 commit into
Open
Conversation
Commit e90b35f modified DateSpan.distance without running Black, so the Lint code with Black workflow fails on master with black ~=24.0 flagging pymeos/collections/time/datespan.py. Reformat only that file with the same Black version the CI uses; no other files are affected.
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
1 participant
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.
Commit e90b35f modified DateSpan.distance without running Black, leaving pymeos/collections/time/datespan.py non Black-clean, so the Lint code with Black workflow fails on master with black ~=24.0 and blocks unrelated PRs. This reformats only that one file with the same Black version the CI uses (24.x), collapsing a single timedelta call onto one line; no other files are touched and there is no behavior change.