summaryrefslogtreecommitdiff
path: root/doc/source/dev/development_environment.rst
diff options
context:
space:
mode:
authorCharles Harris <charlesr.harris@gmail.com>2015-08-29 09:30:34 -0600
committerCharles Harris <charlesr.harris@gmail.com>2015-08-29 10:04:44 -0600
commit529ee89447f03d007498cb2997eec9c93eae83fe (patch)
treec911f149ec35ec72a89a039ea57308f9b1c1abf4 /doc/source/dev/development_environment.rst
parentaa86ff47eeae89e91e7b679e9e50b500b961c584 (diff)
downloadnumpy-529ee89447f03d007498cb2997eec9c93eae83fe.tar.gz
MAINT: Remove references to Bento.
Bento builds are no longer supported, so remove references to that built system.
Diffstat (limited to 'doc/source/dev/development_environment.rst')
-rw-r--r--doc/source/dev/development_environment.rst15
1 files changed, 3 insertions, 12 deletions
diff --git a/doc/source/dev/development_environment.rst b/doc/source/dev/development_environment.rst
index 6221353ce..b09728e03 100644
--- a/doc/source/dev/development_environment.rst
+++ b/doc/source/dev/development_environment.rst
@@ -82,19 +82,12 @@ source tree is to use::
$ python setup.py install --prefix /some/owned/folder
$ export PYTHONPATH=/some/owned/folder/lib/python3.4/site-packages
-Besides ``numpy.distutils``, NumPy supports building with `Bento`_.
-This provides (among other things) faster builds and a build log that's much
-more readable than the ``distutils`` one. Note that support is still fairly
-experimental, partly due to Bento relying on `Waf`_ which tends to have
-non-backwards-compatible API changes. Working versions of Bento and Waf are
-run on TravisCI, see ``tools/travis-test.sh``.
-
Using virtualenvs
-----------------
A frequently asked question is "How do I set up a development version of NumPy
-in parallel to a released version that I use to do my job/research?".
+in parallel to a released version that I use to do my job/research?".
One simple way to achieve this is to install the released version in
site-packages, by using a binary installer or pip for example, and set
@@ -190,15 +183,13 @@ For example to see where in the Python code you are, use ``py-list``. For more
details, see `DebuggingWithGdb`_.
Instead of plain ``gdb`` you can of course use your favourite
-alternative debugger; run it on the python binary with arguments
+alternative debugger; run it on the python binary with arguments
``runtests.py -g --python mytest.py``.
Building NumPy with a Python built with debug support (on Linux distributions
-typically packaged as ``python-dbg``) is highly recommended.
-
+typically packaged as ``python-dbg``) is highly recommended.
-.. _Bento: http://cournape.github.io/Bento/
.. _DebuggingWithGdb: https://wiki.python.org/moin/DebuggingWithGdb