summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorCharles Harris <charlesr.harris@gmail.com>2016-01-15 16:58:22 -0700
committerCharles Harris <charlesr.harris@gmail.com>2016-01-15 16:58:22 -0700
commitc45f3e7d56686590af9b27829a505de709702563 (patch)
treea8bdc704d4cfc9866ded7ea8cd00b0cc4f7dc977 /doc
parent35790f6912bfaa4a1fc963ed5c5ca08761d5f9c0 (diff)
parentfb41f0047c5dbd33b344f51dc3faca4acba45293 (diff)
downloadnumpy-c45f3e7d56686590af9b27829a505de709702563.tar.gz
Merge pull request #7023 from jakirkham/fix_docs_release
DOC: Release 1.11.0 text `code` -> ``code``
Diffstat (limited to 'doc')
-rw-r--r--doc/release/1.11.0-notes.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/release/1.11.0-notes.rst b/doc/release/1.11.0-notes.rst
index cd4f83557..f849ef453 100644
--- a/doc/release/1.11.0-notes.rst
+++ b/doc/release/1.11.0-notes.rst
@@ -70,7 +70,7 @@ raise a ``TypeError``.
New Features
============
-* `np.histogram` now provides plugin estimators for automatically
+* ``np.histogram`` now provides plugin estimators for automatically
estimating the optimal number of bins. Passing one of ['auto', 'fd',
'scott', 'rice', 'sturges'] as the argument to 'bins' results in the
corresponding estimator being used.
@@ -104,8 +104,8 @@ New Features
- np.int_ (long), np.intp
The specification is by precision rather than by C type. Hence, on some
- platforms np.int64 may be a `long` instead of `long long` even if the
- specified dtype is `long long` because the two may have the same
+ platforms np.int64 may be a ``long`` instead of ``long long`` even if the
+ specified dtype is ``long long`` because the two may have the same
precision. The resulting type depends on which C type numpy uses for the
given precision. The byteorder specification is also ignored, the
generated arrays are always in native byte order.
@@ -201,7 +201,7 @@ more such dual contiguous arrays and breaks some existing code as a result.
Note that this also affects changing the dtype by assigning to the dtype
attribute of an array. The aim of this deprecation is to restrict views to
c_contiguous arrays at some future time. A work around that is backward
-compatible is to use `a.T.view(...).T` instead. A parameter will also be
+compatible is to use ``a.T.view(...).T`` instead. A parameter will also be
added to the view method to explicitly ask for Fortran order views, but
that will not be backward compatible.