From 5d9413404017a829aa5ddb52be6019fb63ec5c09 Mon Sep 17 00:00:00 2001 From: Georg Brandl Date: Fri, 26 Feb 2016 19:37:12 +0100 Subject: Closes #25910: fix dead and permanently redirected links in the docs. Thanks to SilentGhost for the patch. --- Doc/extending/extending.rst | 2 +- Doc/extending/index.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'Doc/extending') diff --git a/Doc/extending/extending.rst b/Doc/extending/extending.rst index 8cc41840d7..523dfab70c 100644 --- a/Doc/extending/extending.rst +++ b/Doc/extending/extending.rst @@ -27,7 +27,7 @@ your system setup; details are given in later chapters. avoid writing C extensions and preserve portability to other implementations. For example, if your use case is calling C library functions or system calls, you should consider using the :mod:`ctypes` module or the `cffi - `_ library rather than writing custom C code. + `_ library rather than writing custom C code. These modules let you write Python code to interface with C code and are more portable between implementations of Python than writing and compiling a C extension module. diff --git a/Doc/extending/index.rst b/Doc/extending/index.rst index dd43926450..9eec8c273a 100644 --- a/Doc/extending/index.rst +++ b/Doc/extending/index.rst @@ -32,7 +32,7 @@ approaches to creating C and C++ extensions for Python. .. seealso:: - `Python Packaging User Guide: Binary Extensions `_ + `Python Packaging User Guide: Binary Extensions `_ The Python Packaging User Guide not only covers several available tools that simplify the creation of binary extensions, but also discusses the various reasons why creating an extension module may be -- cgit v1.2.1