black

Black for Python https://github.com/psf/black

The 2000x number is based on a pathological directory in black's repo https://github.com/psf/black/tree/main/profiling which make duplicate-code really slow and a fix was done in pylint 4.1.0 according to pylint's maintainer.

Use black as format on save and you will never have a problem with that. https://github.com/psf/black

Coming from a Meta background (not speaking on behalf of Meta): "package/dependency management" - Everything is checked into a monorepo, and built with [Buck2](https://buck2.build/). There's tooling to import/update packages, but no need to reinvent pip or other package managers. Btw, Buck2 is pretty awesome and supports a ton of languages beyond python, but hasn't gotten a ton of traction outside of Meta. "linting, formatting" - [Black](https://github.com/psf/black) and other public ecosystem tooling is great, no need to develop internally. "why is type checking the exception" - Don't know about Astral, but for Meta / Google, most everyone else doesn't design for the scale of their monorepos. Meta moved from SVN to Git to Mercurial, then forked Mercurial into [Sapling](https://sapling-scm.com/) because simple operations were too slow for

> I appreciate that Black annoyed everyone on our team about the same amount but in different ways. If it did affect people equally, it would be great. Unfortunately, spaces for indentation is an accessibility issue and the Black maintainers are hostile to making this configurable. Normally I am in agreement about minimising configurability, but this isn’t a matter of taste, it is making the Python ecosystem more difficult for some disabled people to participate in. https://github.com/psf/black/issues/2798 Fortunately, Ruff makes this configurable, so you don’t have to choose between autoformatting and accessibility any more.

Line length is definitely configurable. All it takes is adding the following on pyproject.toml[1]: [tool.black] line-length = 100 Aside from matrix-like or column aligned data, the only truly awful thing I've encountered has been broken f-string handling[2]. [1]: Example from https://github.com/pythonarcade/arcade/blob/808e1dafcf1da30f... [2]: https://github.com/psf/black/issues/4389

Yes : https://github.com/psf/black/ is 502

Never heard of it so looked it up: https://github.com/psf/black > Black is the uncompromising Python code formatter. By using it, you agree to cede control over minutiae of hand-formatting. In return, Black gives you speed, determinism, and freedom from pycodestyle nagging about formatting. You will save time and mental energy for more important matters.

IME even better than linters is something like `go fmt` (I work mainly in Python and use https://github.com/psf/black). Rather than forcing you to manually jimmy the code to satisfy the robot, just let the robot make it look the way it wants.

We do actually support direct installation of Git and direct URL dependencies. Like, you can do run `uv pip install` with: ``` black @ git+https://github.com/psf/black ``` We also support editable installs for local directories, like you mentioned: ``` black @ ../black ``` The thing we don't support is using _editable_ installs for Git and direct URL dependencies, like: ``` -e git+https://github.com/psf/black ``` In my experience, these are really rare, and we didn't see a reason to support them.

It does, you'd just have to install a python plugin that registers the autocommand-- or leave out the plugin and register the autocommand yourself. The (n)vim/emacs communities aren't fond of integrating the hot new thing for each language directly into the editor-- I think this is a lesson that comes from being 50 years old! As for whether it would be buggy, I'd doubt it? Unless Black's principle of operation is different from most formatters, it should just write the formatted contents to the file, right? The autocommand you'd use would just run Black on your current file on each save. So where % is Vim's symbol for the name of the currently open file, :silent! suppresses stdout/stderr from the formatter, and :! runs a command: autocmd BufWritePost *.py silent! !<format_cmd> % (Don't quote me on that, but it should be essentially correc