Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation #18

Open
bplimley opened this issue Feb 13, 2017 · 1 comment
Open

Documentation #18

bplimley opened this issue Feb 13, 2017 · 1 comment

Comments

@bplimley
Copy link
Contributor

Via Sphinx?

@bplimley bplimley changed the title Automated documentation Documentation Mar 15, 2017
@bplimley
Copy link
Contributor Author

bplimley commented Mar 15, 2017

Some relevant StackOverflow threads:

Some clarification if you're new to these doc tools:

  • Doxygen automatically generates documentation from your source code, linking classes, functions, etc. However it is primarily designed for C++ and Java and for Python apparently you need doxypy or doxypypy to get it to recognize Python docstrings properly.
  • Sphinx is what is used for the official Python docs. It's prettier than doxygen. Basic Sphinx requires you to write the documentation but with hyperlinks to your code. But there's an autodoc extension that automatically builds documentation from your code, similar to doxygen. Sphinx is built specifically for Python. Mark's "Open sourcing a Python project the right way" link recommends Sphinx.

Regardless of which tool we use, we probably need to reformat our docstrings to make optimal use of the formatting and linking capabilities of the tool.

thjoshi added a commit that referenced this issue Jun 14, 2017
…ion from Robin Johnson. Addresses issues (#1), (#18).
@jccurtis jccurtis modified the milestones: v0.3.0, v1.0.0 Jul 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants