Repository navigation
invalid reST markup in several documents #49061
Description
Activity
Several documents contain invalid reST markup that "leaks" into the
html output (missing ``, incorrect indentation, etc.)
This patch fixes the obvious ones.Many thanks! Applied in r68171.
Did you find those yourself, or with some sort of tool?
I did a search on the .html files using a regular expression, and
manually filtered out the false positives.
The expression used was this "::[^=]|:[a-zA-Z][a-zA-Z0-9]+|`|\.\.\s*\w
+:"
I'll try to come up with a useable tool.Could you also fix the indentation of "Queues" example code at
http://docs.python.org/library/multiprocessing.html#exchanging-objects-between-processes
?Done.
This patch includes some (sort of) checker for suspicious constructs
that resembles markup that has leaked into the final output.It's a new Builder for Sphinx, and works with the docutils nodes, not
the source files directly."doc-Makefile.diff" updates both make.bat and the Makefile, adding a
new target "suspicious".The "ignored.csv" file contains the rules to discard false positives.
"builder.diff" updates builder.py in Sphinx, adding a new builder
implemented in suspicious.py; the source code has some comments
explaining how it's used.Execute
make suspicious, a "suspicious.csv" file is created in build/
suspicious containing one line per issue found.Currently, the only relevant message I get is about the :makevar: role
usage in c-api/init.rst -- looks like docutils doesn't properly
processes it.There is something I don't like in the code -- suspicious.py is
generic, lives inside the Sphinx directory, but knows not to process
the "documenting" directory inside Python [there are too much false
positives there -- most of the examples contain actual reST markup].
But I don't know enough of Sphinx to make it better :(Thanks very much! I've added this to the Python doc tools in r68290.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields: