Asked By – jkp
I’m using Sphinx and the autodoc extension to generate API documentation for my Python modules. Whilst I can see how to nicely document specific parameters, I cannot find an example of how to document a
Does anyone have a good example of a clear way to document these?
Now we will see solution for issue: What is the correct way to document a **kwargs parameter?
subprocess-module’s docs is a good example. Give an exhaustive list of all parameters for a top/parent class. Then just refer to that list for all other occurrences of
This question is answered By – SilentGhost
This answer is collected from stackoverflow and reviewed by FixPython community admins, is licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0