-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
CLN some code cleansing in preprocessing #18686
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
CLN some code cleansing in preprocessing #18686
Conversation
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.
Thanks For the PR @lorentzenchr
Apart from the minor docstring formatting fix (new line removal), I don't find the other changes to be really needed here. Typically the import reordering is something we don't respect and that will be broken in the future anyway. I believe that we usually don't merge that kind of PR, though I can't find a precedent ATM. They create unnecessary merge conflicts, obfuscate git blame, and take review time for very little gain in maintainability / cleanness.
@NicolasHug I do not intent to have a long discussion. Still a few points:
Advantage of clean code:
Is it time for a PR enabling black? |
@NicolasHug I reverted most cosmetic changes. Do you feel more comfortable this way or would you prefer to only have the removal of the |
Seems like part of the changes here are going to be overridden / fixed when applying black anyway? |
Some of them yes. But most of them no. In particular the removal of |
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.
Thanks. Minor comments otherwise LGTM.
I'm not convinced that changes, aside from the noqa removal and docstring fixes, are necessary, but they are also probably not worth debating over.
I opened #20813 with the goal for a streamlined policy for license and coding info. |
43d504b
to
2681b5e
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.
Thanks @lorentzenchr
Reference Issues/PRs
despite #11336 (what's the status of our discussion about using black?)
What does this implement/fix? Explain your changes.
Some code cleansing in the module preprocessing.