STY: fix style error #892
Merged
STY: fix style error #892
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
mj-will
requested review from
GregoryAshton,
ColmTalbot,
adivijaykumar and
asb5468
adivijaykumar
approved these changes
Jan 9, 2025
ColmTalbot
approved these changes
Jan 9, 2025
Ignore the specific error relating to missing whitespace (E226)
Co-authored-by: Colm Talbot <[email protected]>
mj-will
force-pushed
the
maint-fix-flake8
branch
from
bee05e6 to
1b5ecf1
Compare
mj-will
changed the title
ColmTalbot
approved these changes
Jan 9, 2025
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.
Ignore the specific error relating to missing whitespace (E226) in the logging out for bilby_MCMC.
Motivation
After an update to various dependencies,
f"Temp:{ii}<->{ii+1}|"was trigger aflake8error (226) because of missing whitespace around the operator(s) (not sure if it's a specific operator or all of them).Since these operators are actually just part of the logging statement, this error can be ignored.Colm pointed out the issue was the
i+1rather than the string.See e.g. the CI here: https://github.com/bilby-dev/bilby/actions/runs/12686391271/job/35358629525
Changes
Fix the fomatting issue,
Other details
Closes #889