return-missing-description (PDF704)¶
PDF703 parameter-type-mismatch
Next rule →PDF705 return-type-required
Added in 1.0.0
Never fix
Convention
Part of the PDF rule category.
View source · View documentation source · Search issues
Fix is not available.
Rule is disabled if docstring-convention is none or pep257.
What it does¶
Checks that parsed return entries in owning function docstrings include a prose description.
Generator functions are skipped by return-entry rules because their value documentation belongs in yield entries. Stub and abstract functions are also skipped.
Why is this useful?¶
Return documentation should explain the meaning of the returned value.
Ruff compatibility¶
None.
Examples¶
PDF704 reports return entries without descriptions:
docstring-convention = "google"
def function() -> int:
"""Return a value.
Returns:
int:
"""
return 1
PDF704: Line 5: Function return 'return' docstring entry is missing a description
Return entries with descriptions are accepted:
docstring-convention = "google"
def function() -> int:
"""Return a value.
Returns:
int: Result value.
"""
return 1
reST :rtype: fields provide type text but not prose descriptions:
docstring-convention = "rest"
def function() -> int:
"""Return a value.
:rtype: int
"""
return 1
PDF704: Line 4: Function return 'return' docstring entry is missing a description
Generator functions are not checked by return-entry rules:
docstring-convention = "google"
def generate() -> Iterator[int]:
"""Yield values.
Returns:
int:
"""
yield 1
Options¶
None.
PDF703 parameter-type-mismatch
Next rule →PDF705 return-type-required