Stabilize ASYNC240

[ntBre]

No description provided.

[astral-sh-bot]

ruff-ecosystem results

Linter (stable)

ℹ️ ecosystem check detected linter changes. (+0 -5 violations, +0 -0 fixes in 3 projects; 52 projects unchanged)

apache/airflow (+0 -0 violations, +0 -0 fixes)

ruff check --no-cache --exit-zero --no-fix --output-format concise --no-preview --select ALL

agronholm/anyio (+0 -0 violations, +0 -0 fixes)

python-trio/trio (+0 -5 violations, +0 -0 fixes)

- src/trio/_tests/test_path.py:257:68: RUF100 [*] Unused `noqa` directive (non-enabled: `ASYNC240`)
- src/trio/_tests/test_subprocess.py:717:56: RUF100 [*] Unused `noqa` directive (non-enabled: `ASYNC240`)
- src/trio/_tests/test_subprocess.py:719:64: RUF100 [*] Unused `noqa` directive (non-enabled: `ASYNC240`)
- src/trio/_tests/test_subprocess.py:723:64: RUF100 [*] Unused `noqa` directive (non-enabled: `ASYNC240`)
- src/trio/_tests/test_subprocess.py:727:64: RUF100 [*] Unused `noqa` directive (non-enabled: `ASYNC240`)

Changes by rule (1 rules affected)

code	total	+ violation	- violation	+ fix	- fix
RUF100	5	0	5	0	0

Linter (preview)

✅ ecosystem check detected no linter changes.

[ntBre]

Ecosystem changes look good (seems reasonable to have "false positives" when an async library is testing its own code). Not sure what the +0/-0 on the other two projects is about, but the five removed unused-noqa diagnostics make sense.

[amyreese]

Looks like this includes one of your other diffs, so you might want to rebase/clean up before merging.

[ntBre]

Oh oops, I guess I rebased the other branch in the middle of working on this. Thanks!

[dylwil3]

(approved but be sure to rebase 😄 )