summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCharles Harris <charlesr.harris@gmail.com>2020-02-23 07:02:36 -0700
committerGitHub <noreply@github.com>2020-02-23 07:02:36 -0700
commitb2545d01be561f7f8bb71c6064ba48de3d3e8dc1 (patch)
tree301a112679661cc92477e80e7c84521147735443
parentde446a536903f906969a1c5860a32ba11078a5ae (diff)
parentfc743a79d63963e2e3a47f130aba22b18a5ab878 (diff)
downloadnumpy-b2545d01be561f7f8bb71c6064ba48de3d3e8dc1.tar.gz
Merge pull request #15633 from mattip/issue-15629
DOC: remove broken link in f2py tutorial
-rw-r--r--doc/source/f2py/getting-started.rst9
1 files changed, 3 insertions, 6 deletions
diff --git a/doc/source/f2py/getting-started.rst b/doc/source/f2py/getting-started.rst
index c600eee01..27ddbb005 100644
--- a/doc/source/f2py/getting-started.rst
+++ b/doc/source/f2py/getting-started.rst
@@ -29,13 +29,12 @@ either by just in one command or step-by-step, some steps can be
omitted or combined with others.
Below I'll describe three typical approaches of using F2PY.
-The following `example Fortran 77 code`__ will be used for
-illustration:
+The following example Fortran 77 code will be used for
+illustration, save it as fib1.f:
.. include:: fib1.f
:literal:
-__ fib1.f
The quick way
==============
@@ -242,14 +241,12 @@ directive defines special comment lines (starting with ``Cf2py``, for
example) which are ignored by Fortran compilers but F2PY interprets
them as normal lines.
-Here is shown a `modified version of the example Fortran code`__, saved
+Here is shown a modified version of the previous Fortran code, save it
as ``fib3.f``:
.. include:: fib3.f
:literal:
-__ fib3.f
-
Building the extension module can be now carried out in one command::
python -m numpy.f2py -c -m fib3 fib3.f