cpython: e0b9e0ed561a (original) (raw)

Mercurial > cpython

changeset 86179:e0b9e0ed561a 2.7

#19196: Improved cross-references in distutils documentation. [#19196]

Serhiy Storchaka storchaka@gmail.com
date Wed, 09 Oct 2013 14:09:02 +0300
parents 7565df5939de
children 372abcca25fc
files Doc/distutils/apiref.rst Doc/distutils/setupscript.rst
diffstat 2 files changed, 18 insertions(+), 15 deletions(-)[+] [-] Doc/distutils/apiref.rst 17 Doc/distutils/setupscript.rst 16

line wrap: on

line diff

--- a/Doc/distutils/apiref.rst +++ b/Doc/distutils/apiref.rst @@ -989,8 +989,9 @@ directories. simply the list of all files under src, with the names changed to be under dst.

.. function:: split_quoted(s) @@ -1257,8 +1258,8 @@ other utility module. built/installed/distributed -This module provides the :class:Distribution class, which represents the -module distribution being built/installed/distributed. +This module provides the :class:~distutils.core.Distribution class, which +represents the module distribution being built/installed/distributed. :mod:distutils.extension --- The Extension class @@ -1706,8 +1707,8 @@ This module supplies the abstract base c options, is the :meth:run method, which must also be implemented by every command class.

Creating a new Distutils command

--- a/Doc/distutils/setupscript.rst +++ b/Doc/distutils/setupscript.rst @@ -139,7 +139,8 @@ directories, libraries to link with, etc All of this is done through another keyword argument to :func:setup, the :option:ext_modules option. :option:ext_modules is just a list of -:class:Extension instances, each of which describes a single extension module. +:class:~distutils.core.Extension instances, each of which describes a +single extension module. Suppose your distribution includes a single extension, called :mod:foo and implemented by :file:foo.c. If no additional instructions to the compiler/linker are needed, describing this extension is quite simple:: @@ -165,8 +166,8 @@ following sections. Extension names and packages ---------------------------- -The first argument to the :class:Extension constructor is always the name of -the extension, including any package names. For example, :: +The first argument to the :class:~distutils.core.Extension constructor is +always the name of the extension, including any package names. For example, :: Extension('foo', ['src/foo1.c', 'src/foo2.c']) @@ -196,7 +197,8 @@ will compile :file:foo.c to the extens Extension source files ---------------------- -The second argument to the :class:Extension constructor is a list of source +The second argument to the :class:~distutils.core.Extension constructor is +a list of source files. Since the Distutils currently only support C, C++, and Objective-C extensions, these are normally C/C++/Objective-C source files. (Be sure to use appropriate extensions to distinguish C++\ source files: :file:.cc and @@ -232,9 +234,9 @@ linked into the executable. Preprocessor options -------------------- -Three optional arguments to :class:Extension will help if you need to specify -include directories to search or preprocessor macros to define/undefine: -include_dirs, define_macros, and undef_macros. +Three optional arguments to :class:~distutils.core.Extension will help if +you need to specify include directories to search or preprocessor macros to +define/undefine: include_dirs, define_macros, and undef_macros. For example, if your extension requires header files in the :file:include directory under your distribution root, use the include_dirs option::