Author: Maciej Fijalkowski <[email protected]> Branch: extradoc Changeset: r441:6d05f7139d01 Date: 2013-05-27 14:08 +0200 http://bitbucket.org/pypy/pypy.org/changeset/6d05f7139d01/
Log: (kasal) typo diff --git a/numpydonate.html b/numpydonate.html --- a/numpydonate.html +++ b/numpydonate.html @@ -80,8 +80,8 @@ become the de-facto standard for doing any kinds of computations that involve n-dimensional arrays. Please consult the NumPy website for more details.</p> </div> -<div class="section" id="why-does-numpy-on-pypy-makes-sense"> -<h1>Why does NumPy on PyPy makes sense?</h1> +<div class="section" id="why-does-numpy-on-pypy-make-sense"> +<h1>Why does NumPy on PyPy make sense?</h1> <p>NumPy on PyPy makes sense for a couple of reasons: Firstly, it is by far the most requested feature from PyPy. Secondly, PyPy <a class="reference external" href="http://morepypy.blogspot.com/2011/07/realtime-image-processing-in-python.html";>performs well</a> on numerical loads already. Therefore bringing NumPy into the diff --git a/source/numpydonate.txt b/source/numpydonate.txt --- a/source/numpydonate.txt +++ b/source/numpydonate.txt @@ -45,7 +45,7 @@ become the de-facto standard for doing any kinds of computations that involve n-dimensional arrays. Please consult the NumPy website for more details. -Why does NumPy on PyPy makes sense? +Why does NumPy on PyPy make sense? ----------------------------------- NumPy on PyPy makes sense for a couple of reasons: Firstly, it is by _______________________________________________ pypy-commit mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-commit
