andpp/mopidy
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

docs: Minor tweaks

Browse Source
This commit is contained in:
Stein Magnus Jodal 2014-01-11 14:24:10 +01:00
parent 99dff7515c
commit b628825964
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/extensiondev.rst
View File

@ -239,7 +239,7 @@ The root of your Python package should have an ``__version__`` attribute with a
class named ``Extension`` which inherits from Mopidy's extension base class, class named ``Extension`` which inherits from Mopidy's extension base class,
:class:`mopidy.ext.Extension`. This is the class referred to in the :class:`mopidy.ext.Extension`. This is the class referred to in the
``entry_points`` part of ``setup.py``. Any imports of other files in your ``entry_points`` part of ``setup.py``. Any imports of other files in your
extension should be kept inside methods. This ensures that this file can be extension should be kept inside methods. This ensures that this file can be
imported without raising :exc:`ImportError` exceptions for missing imported without raising :exc:`ImportError` exceptions for missing
dependencies, etc. dependencies, etc.
@ -436,7 +436,7 @@ Use of Mopidy APIs
When writing an extension, you should only use APIs documented at When writing an extension, you should only use APIs documented at
:ref:`api-ref`. Other parts of Mopidy, like :mod:`mopidy.utils`, may change at :ref:`api-ref`. Other parts of Mopidy, like :mod:`mopidy.utils`, may change at
any time, and is not something extensions should rely on being stable. any time, and is not something extensions should use.
Logging in extensions Logging in extensions