[voidUpdate]

Do you generally pylint an entire codebase at once though? Why not just the file you are actually working on? Based on the homeassistant results (10.3 hours to lint 17.5k files), it only takes about 2 seconds to pylint a file, which doesn't really feel like enough of a wait to need an entirely new linter

[flyingbeaver09]

hopefully I never have to work with you if you think 2 seconds for libting is fine

[voidUpdate]

and hopefully I never have to work with you if you think that every single second must be spent coding, no seconds allowed for stuff to process in the background when you save a file

[psd1]

A delay of two seconds in my commit hook pushes my blood to the hydraulic pressure of a 70-ton digger.

[odiroot]

Commit hooks just don't make that much sense. Push hooks are much better idea. Once you're done with all your work, linting, last minute adjustments and whatnot, push it and get the checks result. If something goes wrong, your push is blocked.

[lelanthran]

> A delay of two seconds in my commit hook pushes my blood to the hydraulic pressure of a 70-ton digger.

Why though? Surely you have it set up to lint as you edit? I know my neovim installation does that and I see the results in the editor as I type.

If it's a rule that linting needs to be in the commit hook, maybe the linter should write a hash of the files linted somewhere. The commit hook script then only lints those files that have changed since the last lint took place.

[voidUpdate]

Then have it run asynchronously when you save

[deviation]

They may instead be targeting folks that run it in CI.