![]() This is by far the best for automatic API generation in Python (note: shameless self-promotion). This have been criticized many times and for long we didn't have a good fully automatic Python API generator integrated with Sphinx until AutoAPI came, which is a new kid in the block. My opinion is this tool is good for stub generation that will require manual editing, and nothing more. You have options, but my experience with this approach is that it requires way too much configuration, and at the end even after creating new templates, I found bugs and the impossibility to determine exactly what was exposed as public API and what not. You will require to setup a page with the autosummaries, and then manually edit the pages. You can either setup your build system to call sphinx-autogen or setup your Sphinx with the autosummary_generate config. For semi-automatic you have Sphinx autosummary.This is great to write a user guide with embedded API generated elements. For manual API documentation you have Sphinx autodoc.You have three options here: manual, semi-automatic (stub generation) and fully automatic (Doxygen like). Sphinx: The defacto tool for documenting a Python project. For this you can improve the integration between Doxygen and Python using doxypypy. But if you have to deal with other related projects written in C or C++ it could make sense. You generate your content using Doxygen, or you generate your content using Sphinx*.ĭoxygen: It is not the tool of choice for most Python projects. Maybe they expect people using """ to adhere to more Pythonic documentation practices and that would interfere with the special doxygen commands? Honestly, I'm a little surprised at the difference - it seems like once doxygen can detect the comments in # blocks or """ blocks, most of the work would be done and you'd be able to use the special commands in either case. There's no particular Python output mode, but you can apparently improve the results by setting OPTMIZE_OUTPUT_JAVA to YES. ![]() ![]() In that case, you can use the special doxygen commands. Or you can (similar to C-style languages under doxygen) double up the comment marker ( #) on the first line before the member: # pyexample In which case the comments will be extracted by doxygen, but you won't be able to use any of the special doxygen commands. ![]() You can either use the Python documentation string syntax: docstring You can use doxygen to document your Python code. This is documented on the doxygen website, but to summarize here: ![]()
0 Comments
Leave a Reply. |