From: Christopher Allan Webber Date: Wed, 29 May 2013 23:10:09 +0000 (-0500) Subject: Explained more clearly why it's okay for interface classes to be keys. X-Git-Url: https://vcs.fsf.org/?a=commitdiff_plain;h=ea49f37821410e4b46179853965cd9ac4f2b9688;p=mediagoblin.git Explained more clearly why it's okay for interface classes to be keys. This commit sponsored by Nick Glynn. Thank you! --- diff --git a/docs/source/pluginwriter/api.rst b/docs/source/pluginwriter/api.rst index 3bb5f445..66def173 100644 --- a/docs/source/pluginwriter/api.rst +++ b/docs/source/pluginwriter/api.rst @@ -273,7 +273,9 @@ Just write the interface like so:: It's fine to use your interface as the key instead of a string if you -like. +like. (Usually this is messy, but since interfaces are public and +since you need to import them into your plugin anyway, interfaces +might as well be keys.) Then a plugin providing your interface can be like::