Amir MOHAMMADI
--- a/doc/pure_python.rst 0 → 100644
+++ b/doc/pure_python.rst 0 → 100644
+2. It  populated the ``./bin`` directory with all the ``console_scripts`` that you have specified in the ``setup.py``.
+   In our example, this is ``./bin/version.py``.
+
+.. note::
+
+    One thing to note in package development is that when you
+    change the entry points in ``setup.py`` of a package, you need to
+    run ``buildout`` again.
+
+
+Using mr.developer
+==================
+
+One extension that may be useful is `mr.developer`_. It allows to develop *other packages* alongside your "main" package.
+This extension will allow buildout to automatically check out packages from git repositories, and places them into the ``./src`` directory.
+It can be simply set up by adding ``mr.developer`` to the extensions section.
--- a/doc/pure_python.rst 0 → 100644
+++ b/doc/pure_python.rst 0 → 100644
+Again, mr.developer does not automatically place the packages into the ``develop`` list (and neither in the ``eggs``), so you have to do that yourself.
+
+With this augmented ``buidlout.cfg``, the ``buildout`` command will perform the following steps:
+
+1.  It checks out the packages that you specified using ``mr.developer``.
+
+2.  It develops all packages in the ``develop`` section
+    (it links the source of the packages to your local environment).
+
+3.  It will go through the list of ``eggs`` and search for according packages in the following order:
+
+    #. In one of the already developed directories.
+    #. In the python environment, e.g., packages installed with ``pip``.
+    #. Online, i.e., in the ``find-links`` directory, or by default on PyPI_.
+
+4.  It will populate the ``./bin`` directory with all the ``console_scripts`` that you have specified in the ``setup.py``.