Closed mmatthe closed 6 days ago
Yes, I have to check for configuration error (exit code = 2). I'll do it soon (or PR welcome).
Thanks for the report!
+1 for checking the return code when ruff
is executed. As reported in #23, pytest-ruff
isn't compatible with ruff
≥ 0.5.0. I discovered that because ruff check
finds plenty of things to complain about in my source code, but ruff
doesn't complain when invoked as part of pytest
. I'm pretty sure it's because ruff
quits on invocation and sends nothing to stdout
, so pytest-ruff
interprets that as passing.
Fixed and released as 0.4.0!
When the
ruff.toml
file contains syntax errors which cannot be parsed, the ruff checks are silently ignored and no error is printed when run viapytest --ruff
:I would expect that the user is shown the error message from ruff itself. Otherwise, an erroneous ruff.toml file will disable any ruff checks.