written by Eric J. Ma on 2018-11-12 | tags: python code style
Having used Black for quite a while now, I have a hunch that it will continue to surpass its current popularity amongst projects.
It's one thing to be opinionated about things that matter for a project, but don't matter personally. Like code style. It's another thing to actually build a tool that, with one command, realizes those opinions in (milli)seconds. That's exactly what Black does.
At the end of the day, it was, and still is, a tool that has a very good human API - that of convenience.
By being opinionated about what code ought to look like, black has very few configurable parameters. Its interface is very simple. Convenient.
By automagically formatting every Python file in subdirectories (if not otherwise configured so), it makes code formatting quick and easy. Convenient.
In particular, by being opinionated about conforming to community standards for code style with Python, black ensures that formatted code is consistently formatted and thus easy to read. Convenient!
Because of this, I highly recommend the use of black for code formatting.
pip install black
@article{
ericmjl-2018-thoughts-black,
author = {Eric J. Ma},
title = {Thoughts on Black},
year = {2018},
month = {11},
day = {12},
howpublished = {\url{https://ericmjl.github.io}},
journal = {Eric J. Ma's Blog},
url = {https://ericmjl.github.io/blog/2018/11/12/thoughts-on-black},
}
I send out a newsletter with tips and tools for data scientists. Come check it out at Substack.
If you would like to sponsor the coffee that goes into making my posts, please consider GitHub Sponsors!
Finally, I do free 30-minute GenAI strategy calls for teams that are looking to leverage GenAI for maximum impact. Consider booking a call on Calendly if you're interested!