From 96d6badfd7f502a91256e5075830b6a3e3561225 Mon Sep 17 00:00:00 2001 From: Stein Magnus Jodal Date: Sun, 14 Apr 2013 14:05:19 +0200 Subject: [PATCH] docs: More reasons for running 'python setup.py develop' --- docs/contributing.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/contributing.rst b/docs/contributing.rst index b8d2a6f3..97bc46bf 100644 --- a/docs/contributing.rst +++ b/docs/contributing.rst @@ -49,10 +49,16 @@ repo. cd mopidy/ -2. To get a ``mopidy`` executable, run:: +2. To get a ``mopidy`` executable and register all bundled extensions with + setuptools, run:: python setup.py develop + It still works to run ``python mopidy`` directly on the ``mopidy`` Python + package directory, but if you have never run ``python setup.py develop`` the + extensions bundled with Mopidy isn't registered with setuptools, so Mopidy + will start without any frontends or backends, making it quite useless. + 3. Now you can run the Mopidy command, and it will run using the code in the Git repo::