Looks fine to me.
I'm going to guess that you're used to codebases that use an autoformatter.
There's definitely a case to be made for autoformatters in projects with a very large (>100) number of developers, but the price you pay for that is much poorer information density per screenful of code.
For things like tinygrad or sqlite with a small dev team it's possible to use whitespace, style, and formatting to communicate important information, just like mathematicians do. The AMS journals don't autoformat mathematicians' equations!
> I'm going to guess that you're used to codebases that use an autoformatter.
I'm used to Python code being "Pythonic" - which is one of those "I know it when I see it" terms.
Even with autoformatters, it's a choice of what criteria you pick. It's possible to have consistency without enforcing low information density.