summaryrefslogtreecommitdiff
path: root/doc/neps
diff options
context:
space:
mode:
authorRalf Gommers <ralf.gommers@gmail.com>2019-05-22 14:23:57 +0200
committerRalf Gommers <ralf.gommers@gmail.com>2019-05-22 14:23:57 +0200
commit585952843ca35a154a424e45b5314d06ffb13ffc (patch)
treeba8d06b21d8a4d014ec1483b4ac0548c239be76b /doc/neps
parentb6d2e5555b6fbbd7631bab510421d2c0989b1e5e (diff)
downloadnumpy-585952843ca35a154a424e45b5314d06ffb13ffc.tar.gz
DOC: some more tweaks of roadmap text based on review comments.
[ci skip]
Diffstat (limited to 'doc/neps')
-rw-r--r--doc/neps/roadmap.rst9
1 files changed, 3 insertions, 6 deletions
diff --git a/doc/neps/roadmap.rst b/doc/neps/roadmap.rst
index b0d08c11d..2ec0b7520 100644
--- a/doc/neps/roadmap.rst
+++ b/doc/neps/roadmap.rst
@@ -55,11 +55,8 @@ We want to further improve NumPy's performance, through:
- Optimizations in individual functions.
Furthermore we would like to improve the benchmarking system, in terms of coverage,
-easy of use, and publication of the results as part of the docs or website:
-
-- Hardware: find a machine that can reliably run serial benchmarks
-- ASV produces graphs, could we set up a site? Currently at
- https://pv.github.io/numpy-bench/, should that become a community resource?
+easy of use, and publication of the results (now
+`here <https://pv.github.io/numpy-bench>`__) as part of the docs or website.
Website and documentation
-------------------------
@@ -105,7 +102,7 @@ Other functionality
- A backend system for ``numpy.fft`` (so that e.g. ``fft-mkl`` doesn't need to monkeypatch numpy)
- Write a strategy on how to deal with overlap between NumPy and SciPy for ``linalg``
and ``fft`` (and implement it).
-- Deprecate ``np.matrix``
+- Deprecate ``np.matrix`` (very slowly)
.. _`NEP 19`: https://www.numpy.org/neps/nep-0019-rng-policy.html