From ec3710f9b5f9957e57cf11cadac34a8c3e69cc79 Mon Sep 17 00:00:00 2001 From: Dillon Niederhut Date: Fri, 14 Jul 2017 05:37:39 -0500 Subject: DOC: correct formatting of basic.types.html In the documentation for types allowed in numpy, missing spaces around the backticks for fixed-width formatting cause code examples to appear as plain text, or are causing plain text to appear as code. This commit fixes back tick spacing in the 'Extended Precision' section of the 'Data Types' page. --- numpy/doc/basics.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'numpy/doc/basics.py') diff --git a/numpy/doc/basics.py b/numpy/doc/basics.py index 083d55a84..40fb0501e 100644 --- a/numpy/doc/basics.py +++ b/numpy/doc/basics.py @@ -155,11 +155,11 @@ with 80-bit precision, and while most C compilers provide this as their ``long double`` identical to ``double`` (64 bits). NumPy makes the compiler's ``long double`` available as ``np.longdouble`` (and ``np.clongdouble`` for the complex numbers). You can find out what your -numpy provides with``np.finfo(np.longdouble)``. +numpy provides with ``np.finfo(np.longdouble)``. NumPy does not provide a dtype with more precision than C -``long double``s; in particular, the 128-bit IEEE quad precision -data type (FORTRAN's ``REAL*16``) is not available. +``long double`` s; in particular, the 128-bit IEEE quad precision +data type (FORTRAN's ``REAL*16`` ) is not available. For efficient memory alignment, ``np.longdouble`` is usually stored padded with zero bits, either to 96 or 128 bits. Which is more efficient -- cgit v1.2.1 From 3d58387717eeb5d8aebe1d712ddbbd04adef2cb2 Mon Sep 17 00:00:00 2001 From: Dillon Niederhut Date: Thu, 27 Jul 2017 00:03:08 -0600 Subject: DOC: removes extraneous whitespace with escapes [ci-skip] --- numpy/doc/basics.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'numpy/doc/basics.py') diff --git a/numpy/doc/basics.py b/numpy/doc/basics.py index 40fb0501e..b79fb2a86 100644 --- a/numpy/doc/basics.py +++ b/numpy/doc/basics.py @@ -155,11 +155,11 @@ with 80-bit precision, and while most C compilers provide this as their ``long double`` identical to ``double`` (64 bits). NumPy makes the compiler's ``long double`` available as ``np.longdouble`` (and ``np.clongdouble`` for the complex numbers). You can find out what your -numpy provides with ``np.finfo(np.longdouble)``. +numpy provides with ``np.finfo(np.longdouble)``\. NumPy does not provide a dtype with more precision than C -``long double`` s; in particular, the 128-bit IEEE quad precision -data type (FORTRAN's ``REAL*16`` ) is not available. +``long double``\s; in particular, the 128-bit IEEE quad precision +data type (FORTRAN's ``REAL*16``\) is not available. For efficient memory alignment, ``np.longdouble`` is usually stored padded with zero bits, either to 96 or 128 bits. Which is more efficient -- cgit v1.2.1 From 01d5886a5ad760e7a27f2f7d715177fafb3777cd Mon Sep 17 00:00:00 2001 From: Dillon Niederhut Date: Fri, 11 Aug 2017 18:29:37 -0500 Subject: DOC: reverts some escapes [ci-skip] --- numpy/doc/basics.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'numpy/doc/basics.py') diff --git a/numpy/doc/basics.py b/numpy/doc/basics.py index b79fb2a86..76d455cd0 100644 --- a/numpy/doc/basics.py +++ b/numpy/doc/basics.py @@ -155,10 +155,10 @@ with 80-bit precision, and while most C compilers provide this as their ``long double`` identical to ``double`` (64 bits). NumPy makes the compiler's ``long double`` available as ``np.longdouble`` (and ``np.clongdouble`` for the complex numbers). You can find out what your -numpy provides with ``np.finfo(np.longdouble)``\. +numpy provides with ``np.finfo(np.longdouble)``. NumPy does not provide a dtype with more precision than C -``long double``\s; in particular, the 128-bit IEEE quad precision +``long double``s; in particular, the 128-bit IEEE quad precision data type (FORTRAN's ``REAL*16``\) is not available. For efficient memory alignment, ``np.longdouble`` is usually stored -- cgit v1.2.1