pre-commit

[ocefpaf]

@efiring this is one of those PRs that you don't like 😄 Lots of churn!

If you have local changes and this will complicate stuff feel free to just close it. If not, I recommend merging this so next time pre-commit run we will keep the code tidy, it could help with a future refactor.

[efiring]

Looks like it is blacker than black! I see you added two code fixers. Some of the extra commas surprised me, but I guess the advantage is that they signal that the block is not yet closed; there is another bracket or paren on the next line. I don't actually like that business of putting the closing paren on its own line and out-dented--it seems a bit unpythonic, looks more like C formatting--but I can tolerate it. That might be the only black rule that I really dislike.
I like the switch to f-strings and direct dictionary comprehensions without having to do it manually.
My local changes are tentative and not extensive at the moment, so I will merge. I don't think it will be too disruptive.

[ocefpaf]

Looks like it is blacker than black!

It is. There are a few "fixes" from https://github.com/wesleybowman/UTide/pull/95/files#diff-63a9c44a44acf85fea213a857769990937107cf072831e1a26808cfde9d096b9R44 and https://github.com/wesleybowman/UTide/pull/95/files#diff-63a9c44a44acf85fea213a857769990937107cf072831e1a26808cfde9d096b9R7 that are not related to black.

I like the switch to f-strings and direct dictionary comprehensions without having to do it manually.

Those are from https://github.com/wesleybowman/UTide/pull/95/files#diff-63a9c44a44acf85fea213a857769990937107cf072831e1a26808cfde9d096b9R37.