Align codestyle

[gi0baro]

Close #123

[matthiask]

I think this would make a rework of #119 necessary, but that's definitely fine since I still have problems with maturin.

My personal preference is to not install formatters using [project.optional-dependencies] but only referencing them through the pre-commit configuration, for example https://github.com/matthiask/django-content-editor/blob/944b9b8b403ecdcfe520cd088569f52259f57fdd/.pre-commit-config.yaml#L25-L32 because I can reuse the installations between many projects and I do not have to install black / ruff / etc. once for each project, but whatever works.

(I won't get into the specifics of code formatting, that's not an useful discussion. Only this: I try configuring tools as little as possible, but no less. The important part is actually using formatters and linters.)

[Aeron]

Ah, I see now. It came from the fellow Pydantic’s configuration. I wasn’t sure why these particular choices.

I don’t know why Samuel and the contributors went against Black a little. But I don’t think we have any legacy constraints here to break Black’s rules.

As a different example, we could look at the Structlog’s configuration. It’s made differently in both Ruff and Black rules.

We can do something in the middle.

Also, we can expand optional dependencies to give a choice to install linters or do it another way.

[Aeron]

If we don’t want to break or skip the Black’s rules, then it’ll be enough to have line length and target versions:

Suggested change

	[tool.black]
	color = true
	line-length = 120
	target-version = ['py38', 'py39', 'py310', 'py311']
	skip-string-normalization = true
	skip-magic-trailing-comma = true
	[tool.black]
	line-length = 120
	target-version = ['py38', 'py39', 'py310', 'py311']

[lautjy]

2 cents: The closer configs are to black defaults the better it is.

[gi0baro]

@matthiask @Aeron @lautjy thank you all for your comments and feedbacks.
I should have managed to add the majority of your suggestions; regarding black I really prefer to have single quote strings (you type 'em faster) and thus leave the thing to ruff, while on the pre-commit thing I'd like to think about it in a separated discussion.

I'm merging this right now, as in the next few days I'll be AFK, and at least existing open PRs can solve eventual conflicts. I'm obviously open to further enhancements following this PR :)

[lautjy]

Your choice is valid. Just want to add that you could write ' or ", and if you have "format on save" in your IDE, it would run black and automatically convert it to ". So having the default config doesn't force you to change habits - and you will quickly get used to seeing the code (have been thru the change years ago).
IMHO the more repos in default black the better. But at this point we are veering too close to nitpicking. Your repo, your choice :)