Update pre-commit config from trame-cookiecutter

[Jo-Byr]

There was a conflict between the lint rules in pyproject.toml and the pre-commit config, I had to remove some rules from pyproject.toml, which had for consequence to reduce the max line length from 120 to 80, I don't know if this is something we want to keep.

[jourdain]

Thanks for taking a stab an making the repo more up to date with the "standard". If some rules don't make sense, you can remove them...

[Jo-Byr]

@jourdain why do we have both black and ruff ? I think ruff doesn't only take care of line length, but since they both take care of it, shouldn't we either remove black or ignore E501 in ruff ?

Also black has built-in ignored cases, which ruff does not have (comments for example) and this poses problem here.

[jourdain]

Agree, black should not be used now that we are relying in ruff.

I guess that initial list was taken from https://learn.scientific-python.org/development/ and I forgot to remove was a duplicate of mine...

Please feel free to remove black here and in the cookiecutter. Thanks for pointing that out.

[Jo-Byr]

Agree, black should not be used now that we are relying in ruff.

Ruff's formater points out all line-too-long errors, whereas Black "makes a best-effort attempt to adhere to the line-length but avoids automatic line-wrapping in some cases (e.g., within comments)" (ruff documentation). Thus we have multiple E501 errors on :param lines in docstrings and using ruff's formatter would imply either splitting these lines, or adding an ignore comment on every occurence.

But we could also keep black and ruff and ignore E501 errors in ruff's configuration to keep black's behavior on these errors.

[finetjul]

I think we have no argument to go against E501. So I suggest we split the lines.

[Jo-Byr]

@finetjul @jourdain It should be all good now.

[finetjul]

@Jo-Byr did you see those warnings ?

[finetjul]

that uppercase is odd here

[jourdain]

lgtm