MAINT: Black, ruff, pre-commit

[larsoner]

Closes #686

• Format with black
• Add reformatting commit to ignore-revs
• Change from flake8 to ruff
• Add to CIs
• Add to pre-commit config

Should be merged rather than squash-and-merged so that the black reformatting commit is ignored properly.

[larsoner]

I'm going to assume this is some weird GitHub problem and try again tomorrow...

[larsoner]

Ahh, GH is degraded at the moment:

Investigating - We are investigating reports of degraded performance for Git Operations and Pull Requests.
Dec 13, 2022 - 17:39 UTC

[hoechenberger]

Hah, nice!!!

[hoechenberger]

So difficult to read. Time to drop support for Python <3.10 so we can use X | Y instead of Union[X, Y] 😎

No but really, here we'd really gain a usability boost from a switch... maybe next spring or so??

[larsoner]

My vote is to go with whenever MNE-Python switches to 3.10 as the min based on EOL

[larsoner]

I temporarily enabled merge commits for the repo so we can merge this one rather than rebase+merge or squash+merge. I also removed the make flake alias. Okay to "merge commit" when green?

[drammock]

why not split out the black commit as a separate PR? and/or rebase to squash all the other commits in this PR into one, and then rebase-merge?

[hoechenberger]

I temporarily enabled merge commits for the repo so we can merge this one rather than rebase+merge or squash+merge. I also removed the make flake alias. Okay to "merge commit" when green?

Okay with me

[hoechenberger]

why not split out the black commit as a separate PR? and/or rebase to squash all the other commits in this PR into one, and then rebase-merge?

This might actually be the better idea 🤓

[larsoner]

why not split out the black commit as a separate PR? and/or rebase to squash all the other commits in this PR into one, and then rebase-merge?

It's certainly another way to do it, but more work at this point. But since @hoechenberger is also for it, I'll do it that way