it sounds like we might want to look at improving ...
# general
a
it sounds like we might want to look at improving our tooling
f
Respectfully disagree. The fact the tooling has opinions allows us to save time on our own bikeshedding 🙂
a
respectfully disagree! part of the reason i like pants is because we can do things e.g. like set up our repo without regard to source roots and tapping out
src/main
and
src/test
all the time!
h
Well, it's not bikeshedding. We have (had?) a longstanding existing format.
THere was nothing to bikeshed.
👍 1
If the tool was configurable we would have chosen two spaces.
1
f
Yes, I agree with this
h
I think we did not do a good job of communicating and socializing this.
f
but in general, that’s why Black decides to be opinonated
h
OK but Black is not the boss of us...
☝️ 1
Whether we use it or not is our decision... Assuming that it's significantly better than other tools in other ways, it's likely we would have gone with that tradeoff. But it is a tradeoff, and one that wasn't effectively communicated.
1
f
Sorry: I was trying to communicate this in my early messages. Sorry I didn’t use all the best channels
h
For future times: This is the kind of thing (big, disruptive, policy changes) that requires proactive communication: Make sure stakeholders across the community (not just at Twitter) are sought out for opinions. It's not enough to post on Slack and whoever reads it reads it...
f
That’s kind of why I pinged the channel early (although I was told this was a bit too much at the time)
But I’m hearing you: will definitely use pants-devel in the future.
a
4-space indentation is a really huge choice that affects the way every pants developer writes code.