You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme.md
+10-16Lines changed: 10 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ A template setup for a python project.
3
3
4
4
It contains the following:
5
5
1. Setting up a python package
6
-
2.tests for unittest and integration testing
6
+
2.Tests for unittest and integration testing
7
7
3. TravisCI for continuous integration
8
8
4. Generating documentation locally and on readthedocs.org built using Sphinx and Doxygen
9
9
5. Packaging the library for distribution on PyPi
@@ -82,12 +82,9 @@ also need to provide instructions on how to run your code just like you'd explai
82
82
83
83
84
84
### 4. Generating Documentation
85
-
You can only go so far without a good documentation. When there are large project release
86
-
they make sure that they have a great documentation. It helps to build a user base around their library.
87
-
As a library developer you can avoid lots of frustration to users and lots of effort on your part trying to resolve user issues
88
-
by having a good documentation.
89
-
90
-
Here's how to generate good looking documentation on localhost.
85
+
You can only go so far without good documentation. Great library developers make sure that they have great documentation. It helps to build a user base around the library.
86
+
As a library developer, you can avoid lots of frustration to users and lots of effort on your part trying to resolve user issues by having good documentation.
87
+
Here's how to generate good looking documentation on the localhost.
91
88
92
89
```
93
90
cd docs
@@ -121,15 +118,16 @@ your package so that its files are reachable from conf.py.
121
118
Path of my conf.py: docs/source/conf.py
122
119
123
120
Add these two statements so conf.py can access your package.
Extension tell doc generator what kind of stuffs to document and what not.
132
-
For instance, sphinx.ext.viewcode provides link to the code code. Add the following to conf.py
129
+
'extension' tells doc generator what kind of stuff to document and what to ignore.
130
+
For instance, 'sphinx.ext.viewcode' generates link to the source code. Add the following to conf.py
133
131
134
132
```
135
133
# First two are essential to generate the docs, others are optional.
@@ -146,12 +144,8 @@ extensions = [
146
144
147
145
We're done with the configuration. See the source code for [conf.py](docs/source/conf.py). I have done away with the boilerplate stuff and
148
146
149
-
docs/source/index.rst file is like the readme for the documentation. The changes you make to this file
150
-
is seen in your documentation. In this file you define which python source file to document and which not to.
151
-
You can include installation instructions, features, usage code snippets, etc in this file.
152
-
153
-
We built two libraries in this project: mathlib and strlib. We want both to be documented.
154
-
So let's add that to the index.rst above "Indices and tables".
147
+
docs/source/index.rst file is like the readme for the documentation. The changes you make to this file is seen in your generated documentation. In this file, you define which python source files to document. You can include installation instructions, features, usage code snippets, etc in this file.
148
+
We built two libraries in this project: mathlib and strlib. We want both libs to be documented. So let's add that to the index.rst above "Indices and tables".
0 commit comments