diff options
author | Serhiy Storchaka <storchaka@gmail.com> | 2018-10-31 09:14:38 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2018-10-31 09:14:38 (GMT) |
commit | 511747bec3aca4ad7930005e3adece9196c1cd39 (patch) | |
tree | 87d40a581dcbd74c7de48b102d9260473c2a2852 /Doc | |
parent | c9a6168924ffa4f3f78175998b392fe23d3edc50 (diff) | |
download | cpython-511747bec3aca4ad7930005e3adece9196c1cd39.zip cpython-511747bec3aca4ad7930005e3adece9196c1cd39.tar.gz cpython-511747bec3aca4ad7930005e3adece9196c1cd39.tar.bz2 |
bpo-35110: Fix yet few spaces before dashes. (GH-10255)
Diffstat (limited to 'Doc')
-rw-r--r-- | Doc/distutils/configfile.rst | 4 | ||||
-rw-r--r-- | Doc/library/optparse.rst | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/Doc/distutils/configfile.rst b/Doc/distutils/configfile.rst index cd10a7f..0874d05 100644 --- a/Doc/distutils/configfile.rst +++ b/Doc/distutils/configfile.rst @@ -13,8 +13,8 @@ edit is a cheap and easy way to solicit it. Configuration files also let you provide default values for any command option, which the installer can then override either on the command-line or by editing the config file. -The setup configuration file is a useful middle-ground between the setup script ----which, ideally, would be opaque to installers [#]_---and the command-line to +The setup configuration file is a useful middle-ground between the setup +script---which, ideally, would be opaque to installers [#]_---and the command-line to the setup script, which is outside of your control and entirely up to the installer. In fact, :file:`setup.cfg` (and any other Distutils configuration files present on the target system) are processed after the contents of the diff --git a/Doc/library/optparse.rst b/Doc/library/optparse.rst index 4f7bd43..3afc77b 100644 --- a/Doc/library/optparse.rst +++ b/Doc/library/optparse.rst @@ -379,8 +379,8 @@ types is covered in section :ref:`optparse-extending-optparse`. Handling boolean (flag) options ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Flag options---set a variable to true or false when a particular option is seen ----are quite common. :mod:`optparse` supports them with two separate actions, +Flag options---set a variable to true or false when a particular option is +seen---are quite common. :mod:`optparse` supports them with two separate actions, ``store_true`` and ``store_false``. For example, you might have a ``verbose`` flag that is turned on with ``-v`` and off with ``-q``:: |