4 ms·
Of course I'm not sure I'd trust to install or use in my main machine something that has been 100% written by an LLM, that doesn't have enough reviews and scrut
by Lucasoato 4mo ago
Of course I'm not sure I'd trust to install or use in my main machine something that has been 100% written by an LLM, that doesn't have enough reviews and scrutiny, but the numbers look astounding:
codebase pylint prylint speedup
black 26.7 hr 41s 2328×
- smarx007 4mo agoQuite believable if the test was run on a machine with little RAM and generous/unbounded swap. Not sure these are the numbers we want to see. Anything can take days if it swaps to death.
- dgb23 4mo ago"Buy more RAM" usually isn't the thing I want to hear when my linter is slow.
- ndr 4mo agoTBH this is true only on the root of black. If you do `uvx pylint src/` it takes 5s on my machine. It's still impressive but it looks like a pathological case in a test directory.
- mezyt 4mo agohttps://github.com/psf/black/tree/main/profiling https://github.com/psf/black/tree/main/profiling
- ndr 4mo agoYes it's that, in particular `duplicate-code`. `pylint . --disable=R0801` will work, `pylint profiling/ --enable=duplicate-code` doesn't seem to exit in a reasonable time. So that's likely hitting some pathological case, possibly accidentallyquadratic.tumblr.com material.