Skip to content

numpydoc+google: one param per listed name - #182

Merged
rr- merged 1 commit into
mainfrom
rework/40-multi-names
Nov 7, 2026
Merged

rr- merged 1 commit into
mainfrom
rework/40-multi-names

Conversation

@rr-

@rr- rr- commented Nov 6, 2026

Copy link
Copy Markdown
Owner

A head that lists several names now gives one param per name, each with the same type and description:

  • Numpydoc: x, y : int
  • Google: x, y (int): text, and *args, **kwargs: text

Only a head that is a plain list of names (with optional */**) is split, so a head like x, or else (int) stays one param. Compose writes the params one per name, which reads back the same.

Case diffs: 14 corpus cases (numpy, pandas, scipy), all x1, x2-style heads such as axis1, axis2, c1, c2, formats, names, titles, aligned, byteorder and *args, **kwargs, now one param per name.

Parity against origin/main: 15 of 29183 docstrings differ, case 14, stdlib 1 (filecmp.dircmp, whose Google read now gives left_list/right_list and left_only/right_only one param each). No docstring parses only in base, so no stdlib docstring newly makes strict parse raise.

@rr- rr- self-assigned this Nov 6, 2026
A head that lists several names, as in Numpydoc's "x, y : int" or
Google's "x, y (int): text", gave one param named "x, y". It now gives
one param per name, each with the same type and description. Compose
writes them one per name, which reads back the same.
@rr-
rr- force-pushed the rework/40-multi-names branch from ad073b9 to ed1ee0f Compare November 7, 2026 00:39
@rr-
rr- merged commit 7782db0 into main Nov 7, 2026
26 checks passed
@rr-
rr- deleted the rework/40-multi-names branch November 7, 2026 00:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant