Any word out about a version for emacs?
Black: An uncompromising Python code formatter
21–30 of 262 posts
Re: Black: An uncompromising Python code formatter
#22> By using it, you agree to cede control over minutiae of hand-formatting. I may be in a minority, but I do not want to cede control over minutiae of hand-formatting. Am I the only person that feels this way?
Not at all. I would never use something like this except to clean up some sloppy code that I am inheriting.
Sometimes that sloppy code is your own code from yesterday or last week or last month. Tighten that feedback loop and sooner or later you're formatting on save and really happy about it.
Re: Black: An uncompromising Python code formatter
#23Earlier quoted context omitted.
Why black over yapf?
Black is a simple tool. It tries to implement a single code style well. It's not configurable. We tried YAPF before and could never roll it out for everybody. I even contributed the "facebook" style to the tool. There were a few reasons why YAPF didn't work out for us but the most important were: - YAPF would at times not produce deterministic formatting (formatting the same file the second time with no changes in be…
Another issue is that yapf uses an algorithm that is quadratic, so you end up with code you actually see in practice take seconds to minutes to format.
The authors have been adding specific workarounds for some cases but it's a general issue with the approach:
- https://github.com/google/yapf/issues/264
- https://github.com/google/yapf/issues/39
Black algorithm doesn't explode in such way. It's also a lot faster overall which makes it possible and reasonable to enable a good format on save experience.
Re: Black: An uncompromising Python code formatter
#2488 characters per line is a weird choice. Why not 90?
90 characters?!?!? You heathen. I want 132 characters per line.
Re: Black: An uncompromising Python code formatter
#25I find as I write code I no longer worry about alignment or long lines. When I have vim paste a section of code and its at a different indentation I just run black.
Re: Black: An uncompromising Python code formatter
#26At Facebook, we are now using prettier[1] on all our JavaScript files, a growing number of Hack files are formatted with Hackfmt[2] and now black is being rolled out for Python. It's a really exciting time :) [1] https://prettier.io/ [2] https://github.com/facebook/hhvm/blob/master/hphp/hack/src/h...
Hey Vjeux. What does black mean for the prettier python plugin[1]? I had high hopes to move over all projects to prettier (for JS/Python). Is there going to be any merging between prettier python and black? Do you recommend one over the other?
Thanks
Re: Black: An uncompromising Python code formatter
#27Earlier quoted context omitted.
Why black over yapf?
Black is a simple tool. It tries to implement a single code style well. It's not configurable. We tried YAPF before and could never roll it out for everybody. I even contributed the "facebook" style to the tool. There were a few reasons why YAPF didn't work out for us but the most important were: - YAPF would at times not produce deterministic formatting (formatting the same file the second time with no changes in be…
> It's not configurable.
Except for the line length:
> if you're paid by the line of code you write, you can pass --line-length with a lower number.
Re: Black: An uncompromising Python code formatter
#28I like the spirit of it, but the implementation seems to contain too many exceptions (e.g. trailing comma, whilespaces around :). This problem is not unique to Black, it is actually too common for most auto-formatters.
I usually prefer a set of dead-simple formatting/styling rule, easier to enforce, lower cognitive load.
Re: Black: An uncompromising Python code formatter
#29Any word out about a version for emacs?
From the linked GitHub page, it says for Emacs integration use https://github.com/proofit404/blacken . I haven't tried it.
Re: Black: An uncompromising Python code formatter
#30> By using it, you agree to cede control over minutiae of hand-formatting. I may be in a minority, but I do not want to cede control over minutiae of hand-formatting. Am I the only person that feels this way?
I almost always turn off auto-formatting; at least when i can use vim. If i'm force outside of vim (where i don't have a 'shift' operation), then I don't mind it as much; but i almost always hate the way auto-formatted code looks.