summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStefan Behnel <stefan_ml@behnel.de>2014-04-30 20:08:06 +0200
committerStefan Behnel <stefan_ml@behnel.de>2014-04-30 20:21:58 +0200
commit6b5856abfa3aa621f487123e64376cada3418294 (patch)
tree329762fc754ca29c68f01eea9c089fd2bc5366ac
parent1a45f8407e1fb5e12fc81b2562a9c62cdbfb07d3 (diff)
downloadcython-0.20.x.tar.gz
minor doc clarification0.20.x
-rw-r--r--docs/src/quickstart/build.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/src/quickstart/build.rst b/docs/src/quickstart/build.rst
index f71b1b7f9..afcea4f0f 100644
--- a/docs/src/quickstart/build.rst
+++ b/docs/src/quickstart/build.rst
@@ -16,8 +16,8 @@ There are several ways to build Cython code:
were ``.py`` files (using distutils to compile and build in the background).
- Run the ``cython`` command-line utility manually to produce the ``.c`` file
from the ``.pyx`` file, then manually compiling the ``.c`` file into a shared
- object library or ``.dll`` suitable for import from Python.
- (This is mostly for debugging and experimentation.)
+ object library or DLL suitable for import from Python.
+ (These manual steps are mostly for debugging and experimentation.)
- Use the [Sage]_ notebook which allows Cython code inline.
Currently, distutils is the most common way Cython files are built and distributed. The other methods are described in more detail in the :ref:`compilation` section of the reference manual.