咨询Pylint中DESIGN类最大指标的设计依据（三类特定指标）

Great question! Pylint's default complexity and readability thresholds aren't arbitrary—they're built on decades of software engineering research, cognitive psychology insights, and industry-proven best practices. Let's dive into the specific metrics you're curious about, plus the broader context for these limits:

Function/Method Maximum Arguments (max-args=5) #

This limit ties directly to Miller's Law, a cognitive science principle stating that human short-term memory can hold roughly 7±2 pieces of information at once. Since function arguments require understanding not just their count, but their purpose, order, and default values (if any), the lower end of that range (5) is chosen to minimize cognitive overload.

Beyond psychology, this threshold enforces the Single Responsibility Principle: functions with more than 5 arguments often try to do too much. Splitting such functions into smaller, focused ones makes code easier to test, debug, and reuse. Many widely adopted style guides (like Google's Python Style Guide) echo this recommendation to avoid parameter bloat.

Function/Method Maximum Branches (max-branches=12) #

Branch count is closely linked to cyclomatic complexity—a metric that measures the number of distinct execution paths in a function. Research consistently shows that functions with cyclomatic complexity above 10 have a significantly higher risk of bugs and are harder to maintain.

Pylint's 12 threshold is a pragmatic middle ground: it gives developers room to handle reasonable edge cases without letting functions devolve into tangled "spaghetti code". Most static analysis tools set their default complexity limits in the 10-15 range, reflecting industry consensus on balancing functionality and maintainability.

Function/Method Maximum Local Variables (max-locals=15) #

Again, cognitive load is at play here. Tracking the state and purpose of 15+ local variables in a single function strains short-term memory, making it easy to mix up values or lose track of logic flow.

This threshold also signals a code smell: functions with too many local variables often take on multiple responsibilities. Splitting these into smaller functions (each with a clear focus) reduces variable clutter and makes the codebase more approachable. The 15 limit is a practical value derived from real-world development experience, balancing flexibility with readability.

A Quick Note on Other Metrics #

Most of Pylint's default limits (like max-attributes or max-statements) follow the same pattern: they're rooted in classic software engineering texts (such as Clean Code or Code Complete) which distill decades of developer experience and research into actionable guidelines. These books emphasize that limiting complexity directly correlates with long-term code maintainability.

内容的提问来源于stack exchange，提问作者Jean-Francois T.