Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

Change reST targets in setup.cfg spec. 

I chose “setupcfg” as prefix instead of “packaging-setupcfg” because the scope
of the spec is not limited to packaging: it’s intended as a language-agnostic
document for packaging tools developers as well as Python authors.
This commit is contained in:
Éric Araujo 2011-06-06 01:54:54 +02:00
parent f0f9b22459
commit 0300b5c9e6
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Doc/packaging/commandhooks.rst
View File

@ -11,7 +11,7 @@ The pre-hooks are run after the command is finalized (its options are
processed), but before it is run. The post-hooks are run after the command
itself. Both types of hooks receive an instance of the command object.
See also global setup hooks in :ref:`packaging-setupcfg`.
See also global setup hooks in :ref:`setupcfg-spec`.
Sample usage of hooks

6
Doc/packaging/setupcfg.rst
View File

@ -1,6 +1,6 @@
.. highlightlang:: cfg
.. _packaging-setupcfg:
.. _setupcfg-spec:
*******************************************
Specification of the :file:`setup.cfg` file
@ -387,7 +387,7 @@ The final paths where files will be placed are composed by : **source** +
**destination**. In the previous example, **doc/doc.man** will be placed in
**destination_doc/doc/doc.man** and **scripts/foo.sh** will be placed in
**destination_scripts/scripts/foo.sh**. (If you want more control on the final
path, take a look at base_prefix_).
path, take a look at :ref:`setupcfg-resources-base-prefix`).
The **destination** part of resources declaration are paths with categories.
Indeed, it's generally a bad idea to give absolute path as it will be cross
@ -511,7 +511,7 @@ Your **files** section will be::
More control on destination part
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. _base_prefix:
.. _setupcfg-resources-base-prefix:
Defining a base prefix
""""""""""""""""""""""