summaryrefslogtreecommitdiff
path: root/docs/src/userguide/debugging.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/src/userguide/debugging.rst')
-rw-r--r--docs/src/userguide/debugging.rst7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/src/userguide/debugging.rst b/docs/src/userguide/debugging.rst
index 06af18bbf..a33ff8dd8 100644
--- a/docs/src/userguide/debugging.rst
+++ b/docs/src/userguide/debugging.rst
@@ -21,19 +21,20 @@ source, and then running::
make
sudo make install
+Installing the Cython debugger can be quite tricky. `This installation script and example code <https://gitlab.com/volkerweissmann/cygdb_installation>`_ might be useful.
+
The debugger will need debug information that the Cython compiler can export.
This can be achieved from within the setup script by passing ``gdb_debug=True``
to ``cythonize()``::
- from distutils.core import setup
- from distutils.extension import Extension
+ from setuptools import Extension, setup
extensions = [Extension('source', ['source.pyx'])]
setup(..., ext_modules=cythonize(extensions, gdb_debug=True))
For development it's often helpful to pass the ``--inplace`` flag to
-the ``setup.py`` script, which makes distutils build your project
+the ``setup.py`` script, which makes setuptools build your project
"in place", i.e., not in a separate `build` directory.
When invoking Cython from the command line directly you can have it write