My team is considering introducing ruff to our python repo, but we're overwhelmed by the sheer volume of changes to the code that ruff would require, many of them involving manual changes. At the same time we're rushing on product deliverables, so there's no way this upgrade is going to get prioritized in the foreseeable future. Is there some kind of system for grandfathering ruff in so that it applies to new modules but automatically ignores pre-existing ones? Continue reading...
