Skip to content

Conversation

@wedaly
Copy link

@wedaly wedaly commented Jan 4, 2015

This is an attempt to add Sphinx API docs, addressing issue #262.

To generate the documentation locally:

cd docs
pip install -r requirements.txt
make html

Then open _build/html/index.html

To make the docstrings format correctly in the generated API documentation, I've used the napoleon docstring style to specify arguments and return values. This format seemed closest to the current docstring conventions (using "Params") while allowing Sphinx to properly format argument lists and return values.

I moved to the "Install", "Usage", and "Test" sections of the README into the documentation ".rst" files and added a link to ReadTheDocs in the readme. There's a possible race condition here, since someone will need to add the Sphinx documentation to ReadTheDocs before merging this (not sure if that's possible on rtd). If this is an issue, I can split the changes to README.md into a separate pull request.

Please let me know if I need to make any changes. Thank you!

-- Will

docs/conf.py Outdated
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this be pulled in dynamically from the VERSION file ?

@dpkp
Copy link
Owner

dpkp commented Jan 10, 2015

Any thoughts on how to automate doc creation when we tag a new release?

@wedaly
Copy link
Author

wedaly commented Jan 10, 2015

Updated to pull the documentation version dynamically from the VERSION file.

For automating the doc build process, I've used webhooks in the past: http://read-the-docs.readthedocs.org/en/latest/webhooks.html ReadTheDocs uses the documentation version number, so when a new version is specified in the VERSION file, a new version of the documentation will appear on the site.

This does imply that the "latest" version on ReadTheDocs will always be the bleeding edge version of the documentation. I've seen some projects (like Django, for example) include a warning in the development version of the docs, with a link to the docs for the latest stable release.

README.md Outdated
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't look like valid Markdown. Can you update?

@wedaly
Copy link
Author

wedaly commented Jan 15, 2015

Updated the README link to use valid markdown syntax.

dpkp added a commit that referenced this pull request Jan 23, 2015
@dpkp dpkp merged commit 587206f into dpkp:master Jan 23, 2015
@wedaly wedaly deleted the sphinx-api-docs branch January 23, 2015 23:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants