Removed SOCIAL_AUTH_IMPORT_BACKENDS from docs as its deprecated.

diff --git a/README.rst b/README.rst
index 5626fc65b4e12ec45b4e55d5bc336840cc6e4506..9826c2995b4165dbe18fc2dba3d63a88dc20e39c 100644 (file)
--- a/README.rst
+++ b/README.rst
@@ -122,15 +122,6 @@ Configuration
         'django.contrib.auth.backends.ModelBackend',
     )
 
-- The application will try to import custom backends from the sources defined in::
-
-    SOCIAL_AUTH_IMPORT_BACKENDS = (
-        'myproy.social_auth_extra_services',
-    )
-
-  This way it's easier to add new providers, check the already defined ones
-  in ``social_auth.backends`` for examples.
-
   Take into account that backends **must** be defined in AUTHENTICATION_BACKENDS_
   or Django won't pick them when trying to authenticate the user.
 
@@ -295,7 +286,7 @@ Configuration
       SOCIAL_AUTH_CREATE_USERS = False
 
   It is also possible to associate multiple user accounts with a single email
-  address as long as the rest of the user data is unique. Set value as True 
+  address as long as the rest of the user data is unique. Set value as True
   to enable, otherwise set as False to disable.
   This behavior is disabled by default (false) unless specifically set::
 
@@ -354,7 +345,7 @@ raised.
 Also a new-user signal (``socialauth_registered``) is sent when new accounts are
 created::
 
-    from social_auth.signals import socialauth_registered 
+    from social_auth.signals import socialauth_registered
 
     def new_users_handler(sender, user, response, details, **kwargs):
         user.is_new = True
@@ -574,7 +565,7 @@ GitHub works similar to Facebook (OAuth).
 - also it's possible to define extra permissions with::
 
      GITHUB_EXTENDED_PERMISSIONS = [...]
- 
+
 
 -------
 Dropbox

diff --git a/doc/configuration.rst b/doc/configuration.rst
index 5b2e02fb82bfc072d45e7592975656d04f4d9c74..5491453a0b8c2ed7c019c7f7395515b198bbf3b3 100644 (file)
--- a/doc/configuration.rst
+++ b/doc/configuration.rst
@@ -8,7 +8,7 @@ Configuration
         'social_auth'
     )
 
-- Add desired authentication backends to AUTHENTICATION_BACKENDS_ setting::
+- Add desired authentication backends to Djangp's AUTHENTICATION_BACKENDS_ setting::
 
     AUTHENTICATION_BACKENDS = (
         'social_auth.backends.twitter.TwitterBackend',
@@ -26,15 +26,6 @@ Configuration
         'django.contrib.auth.backends.ModelBackend',
     )
 
-- The application will try to import custom backends from the sources defined in::
-
-    SOCIAL_AUTH_IMPORT_BACKENDS = (
-        'myproy.social_auth_extra_services',
-    )
-
-  This way it's easier to add new providers, check the already defined ones
-  in ``social_auth.backends`` for examples.
-
   Take into account that backends **must** be defined in AUTHENTICATION_BACKENDS_
   or Django won't pick them when trying to authenticate the user.