-
Notifications
You must be signed in to change notification settings - Fork 15
Sphinx docs #28
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
Sphinx docs #28
Conversation
|
The current state can be uploaded to readthedocs as soon as the repository is public. I think we have to discuss which parts of the library are meant to be public and as such need intensive documentation and which parts are not meant to be internal and thus do need less documentation. |
|
I get an error when trying to compile the sphinx file with |
|
weird, there is contents.rst in my folder and it should not be required...can you see what happens if you put an empty contents.rst file into the source folder and run the script again? |
|
If I do that it works. Seems like it does quite a reasonable job already for many functions (although some docstrings seem to be randomly missing, not sure why. It prints a lot of warnings but not necessarily on the missing functions. |
|
Yes, we can work through the warnings and see what they are caused by. If some of your files contain code that is not either in a function, class or if name == 'main': condition, then they might be executed during the sphinx inspection. |
|
Ready to merge! |
|
It seems that getting rid of all non-API modules i.e. |
|
You are right, we could just exclude that from the documentation, there is a feature for that. The format is just a theme I think, I will check how to do it from the sphinx source they have at their github repository. |
I set the format style to numpy style, even though we are still far from it. For this to change I certainly need your help to know which parts have to be commented.