diff options
| author | Matthias Bussonnier <bussonniermatthias@gmail.com> | 2022-06-09 00:25:09 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-06-08 15:25:09 -0700 |
| commit | 3523b578f60b4b584f951f0ffaf89703bc3e07b3 (patch) | |
| tree | 0628cd0da56f551cdbf25f976ca3e598404d9359 /doc/source/f2py | |
| parent | 126046f84449fffeb0c75ae88657ce6b90236eee (diff) | |
| download | numpy-3523b578f60b4b584f951f0ffaf89703bc3e07b3.tar.gz | |
DOC: RST Titles Underline reordering (#21677)
* ~ not ^
* = skipped for -
* swap - and = underline in files they are swapped
* * to = in header underline
* - to = and * to - for consitency
* A few more change * -> ~
* use ~ instead of +
* DOC: Fixup `c-api/array.rst` with further ^ with ~ replacement
There is still a fourth level here, which remains using "
Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net>
Diffstat (limited to 'doc/source/f2py')
| -rw-r--r-- | doc/source/f2py/buildtools/meson.rst | 2 | ||||
| -rw-r--r-- | doc/source/f2py/buildtools/skbuild.rst | 4 | ||||
| -rw-r--r-- | doc/source/f2py/usage.rst | 8 |
3 files changed, 7 insertions, 7 deletions
diff --git a/doc/source/f2py/buildtools/meson.rst b/doc/source/f2py/buildtools/meson.rst index 502d3e211..7edc6722f 100644 --- a/doc/source/f2py/buildtools/meson.rst +++ b/doc/source/f2py/buildtools/meson.rst @@ -77,7 +77,7 @@ possible. The easiest way to solve this is to let ``f2py`` deal with it: Automating wrapper generation -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A major pain point in the workflow defined above, is the manual tracking of inputs. Although it would require more effort to figure out the actual outputs diff --git a/doc/source/f2py/buildtools/skbuild.rst b/doc/source/f2py/buildtools/skbuild.rst index f1a0bf65e..0db12e7b4 100644 --- a/doc/source/f2py/buildtools/skbuild.rst +++ b/doc/source/f2py/buildtools/skbuild.rst @@ -29,7 +29,7 @@ We will consider the ``fib`` example from :ref:`f2py-getting-started` section. :language: fortran ``CMake`` modules only -^^^^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~~~ Consider using the following ``CMakeLists.txt``. @@ -52,7 +52,7 @@ The resulting extension can be built and loaded in the standard workflow. ``setuptools`` replacement -^^^^^^^^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~~~~~~~ .. note:: diff --git a/doc/source/f2py/usage.rst b/doc/source/f2py/usage.rst index dbd33e36e..3fae093f8 100644 --- a/doc/source/f2py/usage.rst +++ b/doc/source/f2py/usage.rst @@ -13,7 +13,7 @@ When used as a command-line tool, ``f2py`` has three major modes, distinguished by the usage of ``-c`` and ``-h`` switches. 1. Signature file generation -^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To scan Fortran sources and generate a signature file, use @@ -40,7 +40,7 @@ Among other options (see below), the following can be used in this mode: Overwrites an existing signature file. 2. Extension module construction -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To construct an extension module, use @@ -91,7 +91,7 @@ Here ``<fortran files>`` may also contain signature files. Among other options example, try ``f2py --help-link lapack_opt``. 3. Building a module -^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~ To build an extension module, use @@ -203,7 +203,7 @@ To see whether F2PY generated interface performs copies of array arguments, use larger than ``<int>``, a message about the copying is sent to ``stderr``. Other options -^^^^^^^^^^^^^ +~~~~~~~~~~~~~ ``-m <modulename>`` Name of an extension module. Default is ``untitled``. |