{
"id": "py-function-naming",
"language": "python",
"group": "style",
"listingTitle": "Py function naming",
"title": "Review function naming",
"mvvm": false,
"defaultSeverity": "info",
"legacyGroup": "nim-style",
"why": "Unexpected mixed-case function names make Python APIs less predictable unless an inherited or framework protocol fixes the spelling.",
"suggestion": "Use lower_snake_case for project-owned functions while preserving required external protocol names.",
"version": 5,
"semanticMaturity": "text",
"securityKind": "none",
"taxonomy": [
"style"
],
"requirements": [
"sourceText"
],
"packs": [
"python",
"fastapi"
],
"implementation": "src/languages/python/rules.rs",
"languages": [
"python"
],
"frameworks": [],
"languageVersions": [],
"limitations": [
"HTTP handlers, test lifecycle hooks, AST-style visitor hooks, COM methods, monkey-patch replacements, and methods marked override are excluded.",
"Other dynamically discovered framework callbacks may still require an explicit project lint policy."
]
}