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: docs/source/usage.rst
+15-15Lines changed: 15 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,8 @@ Usage
6
6
Most common options
7
7
-------------------
8
8
9
-
The following exemple uses all most common options to generate ``pydoctor``'s own API docs under the ``docs/api`` folder.
10
-
It will add a link to the project website in all pages header, show a link to source code aside every documented elements and resolve links to standard library objects.
9
+
The following exemple uses all most common options to generate ``pydoctor``'s own API docs under the ``docs/api`` folder.
10
+
It will add a link to the project website in all pages header, show a link to source code aside every documented elements and resolve links to standard library objects.
11
11
12
12
::
13
13
@@ -22,12 +22,12 @@ It will add a link to the project website in all pages header, show a link to so
.. note:: This exemple assume that you have cloned and installed ``pydoctor`` and you are running the ``pydoctor`` build from Unix and the current directory is the root folder of the Python project.
25
+
.. note:: This exemple assume that you have cloned and installed ``pydoctor`` and you are running the ``pydoctor`` build from Unix and the current directory is the root folder of the Python project.
26
26
27
-
.. warning:: The ``--html-viewsource-base`` argument should point to a tag or a commit SHA rather than a branch since line
27
+
.. warning:: The ``--html-viewsource-base`` argument should point to a tag or a commit SHA rather than a branch since line
28
28
numbers aren't going to match otherwise when commits are added to the branch after the documentation has been published.
29
29
30
-
Publish your documentation
30
+
Publish your documentation
31
31
--------------------------
32
32
33
33
``pydoctor`` output are static HTML pages without no extra server-side support.
@@ -84,8 +84,8 @@ Here is an exemple to automatically generate and publish your documentation with
84
84
publish_dir: ./apidocs
85
85
commit_message: "Generate pydoctor documentation"
86
86
87
-
.. note:: As mentionned in the ``actions-gh-pages`` `documentation`__, the first workflow run won't actually publish the documentation to Github pages.
88
-
Github pages needs to be enabled afterwards in the repo settings, select ``gh-pages`` branch, then re-run your workflow.
87
+
.. note:: As mentionned in the ``actions-gh-pages`` `documentation`__, the first workflow run won't actually publish the documentation to Github pages.
88
+
Github pages needs to be enabled afterwards in the repo settings, select ``gh-pages`` branch, then re-run your workflow.
89
89
90
90
The website we'll be at https://(user).github.io/(repo)/
91
91
@@ -99,16 +99,16 @@ Here is an exemple to automatically generate and publish your documentation with
99
99
Document part of your package
100
100
-----------------------------
101
101
102
-
Sometimes, only a couple classes or modules are part of your public API, not all classes and modules need to be documented.
102
+
Sometimes, only a couple classes or modules are part of your public API, not all classes and modules need to be documented.
103
103
104
104
You can choose to document only a couple classes or modules with the following cumulative configuration option::
Link to elements :py:func:`with custom text <twisted:twisted.web.client.urlunparse>` with::
152
152
153
-
:py:func:`with custom text <twisted:twisted.web.client.urlunparse>`
153
+
:py:func:`with custom text <twisted:twisted.web.client.urlunparse>`
154
154
155
155
Link to elements with default label :py:class:`twisted:twisted.web.client.HTTPDownloader` with::
156
156
@@ -179,7 +179,7 @@ You can subclass the :py:class:`pydoctor:pydoctor.zopeinterface.ZopeInterfaceSys
179
179
180
180
--system-class=mylib._pydoctor.CustomSystem
181
181
182
-
System class allows you to dynamically show/hide classes or methods.
182
+
System class allows you to dynamically show/hide classes or methods.
183
183
This is also used by the Twisted project to handle deprecation.
184
184
185
185
See the `Twisted custom class documentation <https://twistedmatrix.com/documents/current/api/twisted.python._pydoctor.TwistedSystem.html>`_. Naviguate to the source code for a better overview.
@@ -192,7 +192,7 @@ Use custom HTML templates
192
192
Currently, custom HTLM templates needs to be handled with some "monkeypatch" that will selectively use the appropriate templates.
193
193
194
194
See the `Twisted custom class documentation <https://twistedmatrix.com/documents/current/api/twisted.python._release.APIBuilder.html>`_. Naviguate to the source code for a better overview.
195
-
The key thing is to apply a patch to the :py:func:`pydoctor:pydoctor.templatewriter.util.templatefile` function before the build.
195
+
The key thing is to apply a patch to the :py:func:`pydoctor:pydoctor.templatewriter.util.templatefile` function before the build.
196
196
197
197
.. note:: Not fully documented, prone to break
198
198
@@ -203,4 +203,4 @@ You can subclass the :py:class:`pydoctor:pydoctor.templatewriter.writer.Template
0 commit comments