-
Notifications
You must be signed in to change notification settings - Fork 429
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
STYLE: Fix codespell issues #3218
Conversation
Hello @jhlegarreta, Thank you for updating !
Comment last updated at 2024-05-16 14:09:07 UTC |
867a7aa
to
2876601
Compare
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.
Hi @jhlegarreta,
Thank yo for this and see below my comments
Can you also rebase this PR? Thank you |
7da7795
to
e635078
Compare
The inline exclude pattern has not made it into a release yet: And adding |
59432c4
to
28d749d
Compare
I am lost by this PR and not sure to understand what you are trying to do. to me, this 2 lines send me opposite message: |
I am sorry I have lost some lines in previous commits, you will want to check the last push force: The codespell inline command would allow to tell to skip the Tests are passing now: failing tests are unrelated. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3218 +/- ##
=======================================
Coverage 83.75% 83.75%
=======================================
Files 153 153
Lines 21343 21348 +5
Branches 3445 3446 +1
=======================================
+ Hits 17876 17881 +5
Misses 2611 2611
Partials 856 856
|
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.
28d749d
to
7b16a78
Compare
I am surprise that |
Ah ok, it has been merged only on March 10. Let's request a release |
It was only merged in March 2024, and there has not been a release yet. So this is ready to go. |
Hi @jhlegarreta, ok, this PR is ready to go. However, I am not comfortable to merge with Codespell CI's failing and Code Format CI failing. All the follow-up PR will then always fail. They are currently green. Not sure what to do here. Not sure that #3216 will fix that. For how long those CI's will fails after merging this PR?
Please share your thought and let's find a solution. |
7b16a78
to
9d2c2b9
Compare
Ok, thank you for this, and I will create the issue. Can you fix code format also: see here: https://github.com/dipy/dipy/actions/runs/9112708491/job/25052537528?pr=3218#step:4:126 |
Fix typo in view parameter `sagital`. Warn about future removal of support. Fixes: ``` Error: ./dipy/viz/streamline.py:10: sagital ==> sagittal Error: ./dipy/viz/streamline.py:45: sagital ==> sagittal Error: ./dipy/viz/tests/test_streamline.py:34: sagital ==> sagittal ``` raised for example in: https://github.com/dipy/dipy/actions/runs/9051840842/job/24868829333?pr=3216#step:4:17 `codespell` does not allow for now inline ignore rules, so add `sagital` to the whitelist to allow the spell check to pass. The word will be removed as soon as a new `codespell` version gets released. Take advantage of the commit to remove the default value from the docstring and rely on the method signature to remove the maintenance burden.
Deprecate `l` parameter name in favor of `step` in PIESNO: check section 2.6 in original paper by Koay et al., 2009 JMRI for further information about its meaning. Fixes: ``` dipy/denoise/noise_estimate.py:26:33: E741 Ambiguous variable name: `l` dipy/denoise/noise_estimate.py:148:5: E741 Ambiguous variable name: `l` ``` raised for example in: https://github.com/dipy/dipy/actions/runs/9051840840/job/24868829334#step:4:117 Take advantage of the commit to remove the default value from the docstring and rely on the method signature to remove the maintenance burden.
9d2c2b9
to
eb861de
Compare
My bad, had not seen that. Fixed. This is then ready to go. |
Failures are unrelated and have been observed in other PRs: |
Thank you @jhlegarreta ! merging |
sagital
l
parameter name in favor ofstep
in PIESNO