Skip to content

Commit 66fec4b

Browse files
Remove sectionauthor and moduleauthor documentation
1 parent 2eae723 commit 66fec4b

File tree

1 file changed

+0
-22
lines changed

1 file changed

+0
-22
lines changed

documentation/markup.rst

Lines changed: 0 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -349,22 +349,6 @@ they are used in the Python documentation.
349349
<https://www.sphinx-doc.org/>`__.
350350

351351

352-
Meta-information markup
353-
-----------------------
354-
355-
.. describe:: sectionauthor
356-
357-
Identifies the author of the current section. The argument should include
358-
the author's name such that it can be used for presentation (though it isn't)
359-
and email address. The domain name portion of the address should be lower
360-
case. Example::
361-
362-
.. sectionauthor:: Guido van Rossum <guido@python.org>
363-
364-
Currently, this markup isn't reflected in the output in any way, but it helps
365-
keep track of contributions.
366-
367-
368352
Module-specific markup
369353
----------------------
370354

@@ -403,12 +387,6 @@ As you can see, the module-specific markup consists of two directives, the
403387
The ``deprecated`` option can be given (with no value) to mark a module as
404388
deprecated; it will be designated as such in various locations then.
405389

406-
.. describe:: moduleauthor
407-
408-
The ``moduleauthor`` directive, which can appear multiple times, names the
409-
authors of the module code, just like ``sectionauthor`` names the author(s)
410-
of a piece of documentation. It too does not result in any output currently.
411-
412390
.. note::
413391

414392
It is important to make the section title of a module-describing file

0 commit comments

Comments
 (0)