From b6844a1e99a2afa3ef7ade0d7bd9fbec6cd9f263 Mon Sep 17 00:00:00 2001
From: Stein Magnus Jodal <stein.magnus@jodal.no>
Date: Fri, 26 Apr 2013 22:21:57 +0200
Subject: [PATCH] docs: A word about codestyle and conventions in extensions

---
 docs/extensiondev.rst | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docs/extensiondev.rst b/docs/extensiondev.rst
index 8044d99d..51168312 100644
--- a/docs/extensiondev.rst
+++ b/docs/extensiondev.rst
@@ -349,6 +349,15 @@ For examples of custom GStreamer elements implemented in Python, see
 :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
 ==================