diff options
| author | Éric Araujo <merwok@netwok.org> | 2011-06-05 23:54:54 (GMT) |
|---|---|---|
| committer | Éric Araujo <merwok@netwok.org> | 2011-06-05 23:54:54 (GMT) |
| commit | 0300b5c9e6dc84b5dd6d2ba26a99832d9397cca7 (patch) | |
| tree | 42205f9aaaff8bc03e68435dede62411454d3a4b /Doc/packaging | |
| parent | f0f9b22459f8d07d04875e31a63287e19c85e243 (diff) | |
| download | cpython-0300b5c9e6dc84b5dd6d2ba26a99832d9397cca7.zip cpython-0300b5c9e6dc84b5dd6d2ba26a99832d9397cca7.tar.gz cpython-0300b5c9e6dc84b5dd6d2ba26a99832d9397cca7.tar.bz2 | |
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.
Diffstat (limited to 'Doc/packaging')
| -rw-r--r-- | Doc/packaging/commandhooks.rst | 2 | ||||
| -rw-r--r-- | Doc/packaging/setupcfg.rst | 6 |
2 files changed, 4 insertions, 4 deletions
diff --git a/Doc/packaging/commandhooks.rst b/Doc/packaging/commandhooks.rst index fd33357..0a3d044 100644 --- a/Doc/packaging/commandhooks.rst +++ b/Doc/packaging/commandhooks.rst @@ -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 diff --git a/Doc/packaging/setupcfg.rst b/Doc/packaging/setupcfg.rst index a195d5a..af90304 100644 --- a/Doc/packaging/setupcfg.rst +++ b/Doc/packaging/setupcfg.rst @@ -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 """""""""""""""""""""" |