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

docs: A word about codestyle and conventions in extensions

Browse Source
This commit is contained in:
Stein Magnus Jodal 2013-04-26 22:21:57 +02:00
parent 8c65f34d01
commit b6844a1e99
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/extensiondev.rst
View File

@ -349,6 +349,15 @@ For examples of custom GStreamer elements implemented in Python, see
:mod:`mopidy.audio.mixers`. :mod:`mopidy.audio.mixers`.
Python conventions
==================
In general, it would be nice if Mopidy extensions followed the same
:ref:`codestyle` as Mopidy itself, as they're part of the same ecosystem. Among
other things, the code style guide explains why all the above examples start
with ``from __future__ import unicode_literals``.
Use of Mopidy APIs Use of Mopidy APIs
================== ==================