docs: Show full exception path

docs/api/frontends.rst

@@ -33,7 +33,7 @@ The following requirements applies to any frontend implementation:
 
 - Such config values MUST be documented.
 
-- The main actor MUST raise the :exc:`~mopidy.exceptions.FrontendError` with a
+- The main actor MUST raise the :exc:`mopidy.exceptions.FrontendError` with a
   descriptive error message if the defined config values are not adequate for
   the frontend to work properly.
 

mopidy/backend/__init__.py

@@ -9,7 +9,7 @@ class Backend(object):
     """Backend API
 
     If the backend has problems during initialization it should raise
-    :exc:`~mopidy.exceptions.BackendError` with a descriptive error message.
+    :exc:`mopidy.exceptions.BackendError` with a descriptive error message.
     This will make Mopidy print the error message and exit so that the user can
     fix the issue.
 

mopidy/mixer.py

@@ -13,7 +13,7 @@ class Mixer(object):
     Audio mixer API
 
     If the mixer has problems during initialization it should raise
-    :exc:`~mopidy.exceptions.MixerError` with a descriptive error message. This
+    :exc:`mopidy.exceptions.MixerError` with a descriptive error message. This
     will make Mopidy print the error message and exit so that the user can fix
     the issue.