add ruff pre-commit#1103
Conversation
|
The only thing you can do here is go slow. First, use From there on out, go bit by bit - autofix missing imports and import order only, check if everything still works. Its not necessarily truly "save", e.g. if file A imports things from file B which it has imported from C, but are not used in B. That will probably reduce the number of warnings extensively already. |
|
For example, start with Autofixing will solve quite alot of "problems", but not some sub-cases ( |
|
Thanks for your input on this. I appreciate it! |
Comes at a "problem": ruff identifies almost 800 errors than cannot be fixed automatically and require user interaction.
This is quite tedious and I cannot address it atm as it is just too much work.
Running ruff with
--unsafe-fixesbrings that number down to just 255 files, but I do not feel comfortable with simply applying those potentially unsafe operations as I am not sure whether the tesitng lib covers all potential issues.@janmayer any idea / input / experience on this?