Dimitri Papadopoulos Orfanos

The error about `ASYNC101` and `ASYNC102`? Also, which exact version of hatch? The latest version is 1.14.0. These rules have indeed been removed from recent versions of ruff, they're even...

I'm afraid I don't have much experience with `async` methods, so I cannot help much. It's just that: * I've seen abstract base classes add `async` to the method definition...

Reproduced in https://github.com/sphinx-doc/sphinx/pull/12250. Removing `target-version = "py39"` from `.ruff.toml` breaks the tests as `requires-python = ">=3.9"` from `pyproject.toml` is **not** taken into account. I think ruff should take into account...

Same issue in https://github.com/jaraco/skeleton/issues/119. The situation is even worse here, as `requires-python` is defined in `setup.cfg` instead of `pyproject.toml`. The rationale for a `ruff.toml` file separate from `pyproject.toml` is described...

In the documentation, [Config file discovery](https://docs.astral.sh/ruff/configuration/#config-file-discovery) reads: > Unlike [ESLint](https://eslint.org/docs/latest/user-guide/configuring/configuration-files#cascading-and-hierarchy), Ruff does not merge settings across configuration files; instead, the "closest" configuration file is used, and any parent configuration files...

My suggestion would be to: 1. Keep a single configuration file for _ruff_ itself, that is, disregard the `[tool.ruff]` subtable in `pyproject.toml` if files `.ruff.toml` or `ruff.toml` exist - or...

@Winand I may be wrong, but I think this issue is specifically about taking into account `requires-python` from `pyproject.toml` when using `ruff.toml`. If so, your issue seems slightly different.

@MementoRC Which push to master? I don't have rights to push to this repository, especially without passing checks.

Looks good, now we need to fix one last issue on macOS: ``` delocate.libsana.DelocationError: Library dependencies do not satisfy target MacOS version 10.9: /private/var/folders/vk/nx37ffx50hv5djclhltc26vw0000gn/T/tmpu9qpg5w_/wheel/coincurve/_cffi_backend.cpython-39-darwin.so has a minimum target of 10.13...

`macos-14-large` is only for paying customers. `macos-14` worked for me in a different project — or so it seemed…