Skip to content

rest+epydoc: fix keyword fields and blank lines - #189

Merged
rr- merged 2 commits into
mainfrom
rework/54-rest-epydoc-fields
Nov 7, 2026
Merged

rr- merged 2 commits into
mainfrom
rework/54-rest-epydoc-fields

Conversation

@rr-

@rr- rr- commented Nov 7, 2026 •

Copy link
Copy Markdown
Owner

Covers these items from the BEHAVIOR.md review for #136.

  • ReST reads :key: as a param, as Sphinx does, and :kwarg: and :kwparam: as keywords. Before, :key: was read as a keyword and :kwarg: gave a plain text item.
  • In ReST, an empty :rtype: or :ytype: is now ignored. It used to set the return type to "".
  • Epydoc keeps blank lines in a field's description, as ReST does, so paragraphs and code blocks no longer run together.

Case diffs: three files.

  • rest/compose_keeps_param_kind_01: :key y: is now a param.
  • auto/whitespace_blank_line/form-feed and tab: an Epydoc field keeps its blank line.

Parity against origin/main: 1114 of 29184 docstrings differ (case 3, stdlib 0, the rest generated). The generated ones are mixed-style inputs whose Epydoc fields now keep their blank lines. The parse diffs are all in EPYDOC and AUTO, and the compose diffs follow from them.

ReST read 🔑 as a keyword and did not know :kwarg: or :kwparam:.
As in Sphinx, 🔑 is now a param and the other two are keywords. An
empty :rtype: or :ytype: is ignored instead of giving the type "".

Epydoc dropped the blank lines in a field's description, so its
paragraphs ran together. It now keeps them, as ReST does.
@rr- rr- self-assigned this Nov 7, 2026
@rr-
rr- merged commit b81ef97 into main Nov 7, 2026
26 checks passed
@rr-
rr- deleted the rework/54-rest-epydoc-fields branch November 7, 2026 10:13
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