summaryrefslogtreecommitdiff
path: root/numpy/doc
diff options
context:
space:
mode:
authorCharles Harris <charlesr.harris@gmail.com>2017-08-12 12:57:04 -0500
committerGitHub <noreply@github.com>2017-08-12 12:57:04 -0500
commit019212996b70e50a535755ea01dd40acd1a1335d (patch)
treed9fca9c31152487f2440b780f3f03e11b70ba1a9 /numpy/doc
parentb094453b73a3bf707e2e9864f45f8357e759763c (diff)
parent1f291b8eee4bd3d7a343f03617e5fac40d8dbb36 (diff)
downloadpython-numpy-019212996b70e50a535755ea01dd40acd1a1335d.tar.gz
python-numpy-019212996b70e50a535755ea01dd40acd1a1335d.tar.bz2
python-numpy-019212996b70e50a535755ea01dd40acd1a1335d.zip
Merge branch 'master' into fix-note-on-quad-prec
Diffstat (limited to 'numpy/doc')
-rw-r--r--numpy/doc/basics.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/numpy/doc/basics.py b/numpy/doc/basics.py
index 4943aa227..d0d384a62 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.
+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