Products · Product
pylint
Raised as a usability problem by 7 people on Hacker News over 13 years (2011–2023), in 6 threads.
People raised many different problems with pylint, but no single problem has yet been raised by 3 people in 3 different months and threads.
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 7 complaints
- Pylint takes minutes to check a codebase, too slow to use comfortably2023-02-11
- Default settings produce noisy reports, requiring huge configuration to get sane output2022-10-25
- Pylint is unusable without a good config file2019-07-17
- Warns about things that aren't actual problems, making it hard to use as a clean build gate2016-10-20
- Pylint throws false errors on third-party modules like SQLAlchemy and NumPy, which is frustrating and tedious to configure2016-10-20
- Configuring Pylint is annoying and takes effort2015-06-26
- Linter flags valid code like tuple unpacking and framework patterns, forcing workarounds2011-07-12