@@ -139,7 +139,8 @@ directories, libraries to link with, etc.).
139139
140140 All of this is done through another keyword argument to :func: `setup `, the
141141:option: `ext_modules ` option. :option: `ext_modules ` is just a list of
142- :class: `Extension ` instances, each of which describes a single extension module.
142+ :class: `~distutils.core.Extension ` instances, each of which describes a
143+ single extension module.
143144Suppose your distribution includes a single extension, called :mod: `foo ` and
144145implemented by :file: `foo.c `. If no additional instructions to the
145146compiler/linker are needed, describing this extension is quite simple::
@@ -165,8 +166,8 @@ following sections.
165166Extension names and packages
166167----------------------------
167168
168- The first argument to the :class: `Extension ` constructor is always the name of
169- the extension, including any package names. For example, ::
169+ The first argument to the :class: `~distutils.core. Extension ` constructor is
170+ always the name of the extension, including any package names. For example, ::
170171
171172 Extension('foo', ['src/foo1.c', 'src/foo2.c'])
172173
@@ -196,7 +197,8 @@ will compile :file:`foo.c` to the extension :mod:`pkg.foo`, and :file:`bar.c` to
196197Extension source files
197198----------------------
198199
199- The second argument to the :class: `Extension ` constructor is a list of source
200+ The second argument to the :class: `~distutils.core.Extension ` constructor is
201+ a list of source
200202files. Since the Distutils currently only support C, C++, and Objective-C
201203extensions, these are normally C/C++/Objective-C source files. (Be sure to use
202204appropriate extensions to distinguish C++\ source files: :file: `.cc ` and
@@ -232,9 +234,9 @@ linked into the executable.
232234Preprocessor options
233235--------------------
234236
235- Three optional arguments to :class: `Extension ` will help if you need to specify
236- include directories to search or preprocessor macros to define/undefine:
237- ``include_dirs ``, ``define_macros ``, and ``undef_macros ``.
237+ Three optional arguments to :class: `~distutils.core. Extension ` will help if
238+ you need to specify include directories to search or preprocessor macros to
239+ define/undefine: ``include_dirs ``, ``define_macros ``, and ``undef_macros ``.
238240
239241For example, if your extension requires header files in the :file: `include `
240242directory under your distribution root, use the ``include_dirs `` option::
0 commit comments