unnamed-thread
Threads without names are hard to identify in debugging tools
Applies to: Python
Why this matters
When you create a thread without a name, it shows up as 'Thread-1', 'Thread-2', etc. in debuggers and logs. Naming your threads makes it much easier to understand what each thread is doing when debugging issues.
Catch it before it ships
pip install stablestack # or: npx stablestackstablestack # scans your project, QUAL002 includedstablestack explain QUAL002QUAL002 is part of the Pro rule set. See pricing — the free tier ships 24 checks with no signup.
False positive in your codebase? Suppress a single line with # noqa: QUAL002
More Code Quality checks
exception-swallowing
Silently swallowed exceptions hide bugs and make debugging hard
QUAL003complex-tuple
Tuples with 3+ elements are hard to understand - use a dataclass instead
QUAL004mutable-default-argument
Mutable default arguments are shared between calls and cause bugs
QUAL005print-statement
Print statements are typically debugging code that shouldn't be committed
QUAL006todo-comment
TODO/FIXME comments indicate incomplete or problematic code
QUAL007broad-exception
Catching all exceptions hides bugs and makes debugging hard
QUAL008magic-number
Magic numbers make code hard to understand and maintain
QUAL009file-too-long
File exceeds recommended maximum length.