Ruff linter

[CompRhys]

Addresses #534. Much faster linting and formatting using 1 tool as opposed to 3.

[ilyes319]

Hey @CompRhys, looking at your changes, some of them will break compatibility with Python version 3.7 and 3.8.

[CompRhys]

I ran with target-version = "py37" and so I would assume that nothing would be broken. If you want to keep backwards compatibility to 3.7 would you take a PR adding a CI matrix as I shouldn't be installing an end-of-life python version without security fixes on work laptop?

[ilyes319]

I think these kind of type hints: str | Path | None are not supported with older python versions. Why do you want to change the way we do type hints?

[janosh]

I think these kind of type hints: str | Path | None are not supported with older python versions.

they are actually, if you add from __future__ import annotations to the start of a module (inserting that import can be automated with ruff). it backports the leaner type annotations to 3.7

[ilyes319]

Good to know. Is there any guidelines from Python to prefere these kind of annotations?

[CompRhys]

The pep for it was https://peps.python.org/pep-0604/ generally I think the preference has been to move towards not needing to explicitly import anything in order to type hint standard types such as list, str or combinations thereof.

[janosh]

Is there any guidelines from Python to prefer these kind of annotations?

yes, from __future__ import annotations is only necessary below 3.10. above, the new syntaxes works without side-effect imports which is part of python's move to enable more type safety

[CompRhys]

closing as it seems that there's no interest from maintainers