File: usage.rst

package info (click to toggle)
python-sphinx-code-include 1.1.1-4
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,272 kB
  • sloc: javascript: 8,765; python: 1,270; makefile: 23
file content (134 lines) | stat: -rw-r--r-- 4,255 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
=====
Usage
=====

Configuration
=============

To use Sphinx Code Include in a project

- Create a Sphinx project if you haven't already (using ``sphinx-quickstart`` or otherwise)
- Add ``sphinx-code-include`` to your conf.py


.. code-block :: python

    extensions = [
        "code_include.extension",
    ]


Options
=======

This block shows every option that you can add into a ``code-include`` block.

::

    .. code-include :: :func:`module_name.foo`
        :language: python
        :link-at-bottom:
        :link-to-documentation:
        :link-to-source:
        :no-unindent:

Here's a description of what each option does.

 ======================= ==============================================================================================================================
         Option                                                                   Description
 ======================= ==============================================================================================================================
  language                The syntax highlight that will be used. Examples of valid input in `pygment's documentation`_. The default value is "python"
  link-at-bottom          Add source code and/or documentation links at the bottom of the block.
  link-to-documentation   Add a clickable link to where the source code's API documentation is.
  link-to-source          Add a clickable link to where the source code is from.
  no-unindent             If the found source-code has indentation, don't remove any of it.
 ======================= ==============================================================================================================================


Advanced Usage
==============

If you have to use ``link-to-source``, 2 things are required.

- Your project `must be set up for intersphinx`_.
- The project that you're trying to reference must have
  ``sphinx.ext.viewcode`` included in their extensions.


Example Project
===============

``sphinx-code-include`` shows how to use the ``code-include`` directive
in its own documentation.

This page includes this in its text:

::

    .. code-include :: :mod:`conf`


And this is the conf.py that generates this documentation.

.. code-include :: :mod:`conf`


Notice ``intersphinx_mapping`` towards the bottom. This attribute must
be set up to point to your other project. ``intersphinx_mapping`` cannot
be empty. In our case, we'll point it to some external Sphinx project.

::

    .. code-include :: :func:`requests.get`

And this is what the block above renders as:

.. code-include :: :func:`requests.get`

Notice that `requests.get`_ is actually using a different theme than
this documentation's theme but it still renders with the correct color
scheme.

And of course, you can refer to objects in your current project using
``code-include``, too.

::

    .. code-include :: :func:`code_include.helper.memoize`

.. code-include :: :func:`code_include.helper.memoize`


Advanced Customization - Pre-Processor Function
===============================================

You have total control over how source-code is rendered in your Sphinx
project. Say, for example, you want to get source-code of a function but
you want to remove the function's docstring, or delete its comments.

.. note ::

    code_include_preprocessor is only run if your code comes from
    another Sphinx project. If the source-code that you're targetting
    comes from imported content then the pre-processor is ignored.


Add a function called ``code_include_preprocessor`` to your conf.py

.. code-block :: python

    def code_include_preprocessor(soup):
        """`soup` is a :class:`bs4.element.Tag` object."""
        pass

``code-include`` brings in the source-code from projects as HTML tags.
This function lets you directly access and modify those tags before it
gets converted into raw text. So you're free to change whatever you
want and it will be applied to every code-include directive.


.. _must be set up for intersphinx: http://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html

.. _pygment's documentation: http://pygments.org/docs/lexers

.. _requests.get: https://requests.kennethreitz.org/en/latest/_modules/requests/api/#get