ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

I adjusted the implementation to accept type: ignore comments on the start and end lines of the diagnostic range. I understand that this matches mypy's behavior #15046 (comment).

However, this in itself won't be sufficient for mypy compatibility. We'd also have to match mypy's diagnostic range which we currently don't for invalid assignments (#15046 (comment)). But that's a problem out of this PR's scope

Something for tomorrow. I want to take another look why we need to test both the start and the end. Ruff only tests the start. Testing both might be a problem for a future linter if we have

if True:
	print("test")
else: 
	pass  # knot: ignore

because the ignore on the pass would now ignore any error that applies to the entire else-clause.

Not supporting end positions does seem unintuitive. For example, the following wouldn't work

y = (
    4 /
    0  # type: ignore
)

We should push users towards using specific error codes to mitigate the issue that I pointed out in #15046 (comment)

We should push users towards using specific error codes

And try to avoid overly-large diagnostic ranges. In particular, I suspect we should try to avoid diagnostic ranges on statements, because I think those are the cases where the end is least intuitive.