summaryrefslogtreecommitdiff
path: root/docs/source
diff options
context:
space:
mode:
authorKonrad Delong <konryd@gmail.com>2010-08-13 18:40:49 +0200
committerKonrad Delong <konryd@gmail.com>2010-08-13 18:40:49 +0200
commit422411b2ae522198d665d6f02d07d145eba7990a (patch)
treecc84ecf36b1dbed040de9937c6dfa3e63d87b503 /docs/source
parent77b1b608cd631e6b8236e549bc8dc4327fbcb7e2 (diff)
downloaddisutils2-422411b2ae522198d665d6f02d07d145eba7990a.tar.gz
oh noez! whitespace!
Diffstat (limited to 'docs/source')
-rw-r--r--docs/source/distutils/newcommands.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/source/distutils/newcommands.rst b/docs/source/distutils/newcommands.rst
index a601145..34b3048 100644
--- a/docs/source/distutils/newcommands.rst
+++ b/docs/source/distutils/newcommands.rst
@@ -14,7 +14,7 @@ testing before they are deployed for downloading or use, it's often useful
to be able to run a project's unit tests without actually deploying the project
anywhere. The ``test`` command runs
project's unit tests without actually deploying it, by temporarily putting the
-project's source on ``sys.path``, after first running ``build_ext -i``
+project's source on ``sys.path``, after first running ``build_ext -i``
to ensure that any C extensions are built.
You can use this command in one of two ways: either by specifying a
@@ -26,13 +26,13 @@ names that will be resolved into actual objects.
``--suite=NAME, -s NAME``
Specify the test suite (or module, class, or method) to be run
(for example ``some_module.test_suite``). The default for this option can be
- set by in your ``setup.cfg`` file.
+ set by in your ``setup.cfg`` file.
[test]
suite = my_package.tests.test_all
``--runner=NAME, -r NAME``
- Specify the test runner to be called.
+ Specify the test runner to be called.
``upload`` - Upload source and/or binary distributions to PyPI