Why Does Python Prefer Snake_case? History and Benefits Explained

Variable naming is a frequent debate among programmers. This article examines the different naming conventions, focusing on why Python recommends snake_case.

Single‑character or single‑word variable names can be all lowercase, all uppercase, or capitalized, mirroring English usage.

When multiple words are needed, languages cannot use spaces, so developers created various conventions:

snake_case

camelCase

Hungarian notation

PascalCase

spinal‑case

studly caps

camel‑snake case

All these aim to eliminate spaces and form a new “word”.

The most popular are camelCase and snake_case. Their pros and cons:

Readability: snake_case uses underscores for clear separation; camelCase is more compact.

Ease of typing: camelCase relies on case changes; snake_case uses only lowercase and underscores.

Clarity for acronyms: all‑caps acronyms (HTTP, RGB) may look odd in strict camelCase or snake_case.

Python recommends snake_case for package, module, function, and variable names, while camelCase is used for class names, type variables, and exceptions.

The primary reason is historical: snake_case originated in the 1960s, adopted from C, and was later named “snake_case” in the early 2000s. Python inherited this convention early and also favors the underscore character, which appears in many special identifiers.

Thus, Python’s preference for snake_case stems from tradition and its extensive use of the underscore.