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

Many API docs do not show up in readthedocs #112

Closed
uniomni opened this issue Feb 27, 2012 · 4 comments
Closed

Many API docs do not show up in readthedocs #112

uniomni opened this issue Feb 27, 2012 · 4 comments
Assignees

Comments

@uniomni
Copy link
Contributor

uniomni commented Feb 27, 2012

See for example
http://risk-in-a-box.readthedocs.org/en/latest/api-docs/gui/riab.html
which does not show up.
But
http://risk-in-a-box.readthedocs.org/en/latest/api-docs/gui/riabexceptions.html
does

When generating the html locally they all work

@ghost ghost assigned ted-dunstone Feb 27, 2012
@ted-dunstone
Copy link
Contributor

Might be a silly question but your sure they are checked in to the relavent
branch.
Ted

On Mon, Feb 27, 2012 at 2:46 PM, Ole Nielsen <
reply@reply.github.com

wrote:

See for example
http://risk-in-a-box.readthedocs.org/en/latest/api-docs/gui/riab.html
which does not show up.
But

http://risk-in-a-box.readthedocs.org/en/latest/api-docs/gui/riabexceptions.html
does

When generating the html locally they all work


Reply to this email directly or view it on GitHub:
https://github.com/AIFDR/risk_in_a_box/issues/112

@uniomni
Copy link
Contributor Author

uniomni commented Feb 28, 2012

Good point - however, all of this is happening in master and I could see other changes taking place. The problem is with some of the sections where docstrings are harvested. Very weird.

@timlinux
Copy link
Contributor

Just to update this (since the project name was refactored), an example URL is here:

http://inasafe.readthedocs.org/en/latest/api-docs/gui/is_keywords_dialog.html

My local copy shows the full api docs. Note that I have carefully gone through sphinx warnings/errors and fixed them so I don't think it can be attributed to something broken in the docs. My best bet would be that RTD is not able to parse the source files for some reason.

@ghost ghost assigned timlinux May 16, 2012
@timlinux
Copy link
Contributor

Closing this - all docs are showing nicely for me on InaSAFE.org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants