DOC better installation guidelines

NelleV · NelleV · commit 6c2748bce207 · 2016-10-10T17:21:52.000-07:00
* more stress on setting up virtual environments
* underlined the fact that changing branches may affect c code
diff --git a/doc/devel/gitwash/matplotlib_for_dev.rst b/doc/devel/gitwash/matplotlib_for_dev.rst
@@ -15,10 +15,13 @@ or::
   
    pip install -v -e .
 
-This installs matplotlib for development (i.e., builds everything and places the
-symbolic links back to the source code). Note that this command has to be
-called everytime a `c` file is changed.
+This installs matplotlib for development (i.e., builds everything and places
+the symbolic links back to the source code). This command has to be called
+everytime a `c` file is changed. Note that changing branches may change the
+`c`-code.
 
-You may want to consider setting up a `virtual environment
+When working on bleeding edge packages, setting up a
+`virtual environment
 <http://docs.python-guide.org/en/latest/dev/virtualenvs/>`_ or a `conda
-environment <http://conda.pydata.org/docs/using/envs.html>`_
+environment <http://conda.pydata.org/docs/using/envs.html>`_ is recommended.
+
