-
Notifications
You must be signed in to change notification settings - Fork 371
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
pre-commit: adopt black hook #2152
Conversation
I'll resolve the conflicts in this PR once #2150 is merged |
In general, 👍 from me. I also looked into it a couple years ago :) https://github.com/greglucas/cartopy/tree/black (2021) This should get more buy-in from other devs though too. |
I think black turns too much sensibly formatted code into outright garbage. With that said, I won't stand in the way. But I'm also not going to be clicking the green button on this. |
@dopplershift Yup, totally understand your PoV 👍 Thanks for your candid honesty. I appreciate that I'm happy either way, if this PR lands or not. What I'm attracted to about I appreciate that this PR will be a bit marmite, and I don't want to rock the |
GitHub Discussions now offers Polls, where it's super easy to garner opinions from the community. I was just wondering whether it was worth while enabling GH Discussions for I'm conscious that @SciTools/cartopy-admins How do you guys typically field community wide opinion, or isn't it a done thing? |
I am one of the semi-indifferent people on Black, neither greatly for nor against it, but probably slightly lean in favor because of a similar sentiment to your comment about removing discussion/debate about formatting:
I personally don't think we need another avenue for communication. Cartopy doesn't get a ton of use from the current channels available, so adding another one probably wouldn't get much response either is my guess. |
Conflicts resolved 👍 |
This PR adds support for the black pre-commit git hook to enforce opinionated code formatting throughout the code-base.
Reference: #1934