Ticket #12880: qualified_names.diff

docs/howto/auth-remote-user.txt

@@ -76 +76 @@
 Attributes
 ~~~~~~~~~~
 
-.. attribute:: RemoteUserBackend.create_unknown_user
+.. attribute:: django.contrib.backends.RemoteUserBackend.create_unknown_user
 
     ``True`` or ``False``.  Determines whether or not a
     :class:`~django.contrib.auth.models.User` object is created if not already
@@ -85 +85 @@
 Methods
 ~~~~~~~
 
-.. method:: RemoteUserBackend.clean_username(username)
+.. method:: django.contrib.backends.RemoteUserBackend.clean_username(username)
 
    Performs any cleaning on the ``username`` (e.g. stripping LDAP DN
    information) prior to using it to get or create a
    :class:`~django.contrib.auth.models.User` object.  Returns the cleaned
    username.
 
-.. method:: RemoteUserBackend.configure_user(user)
+.. method:: django.contrib.backends.RemoteUserBackend.configure_user(user)
 
    Configures a newly created user.  This method is called immediately after a
    new user is created, and can be used to perform custom setup actions, such

docs/topics/db/transactions.txt

@@ -171 +171 @@
 
 Savepoints are controlled by three methods on the transaction object:
 
-.. method:: transaction.savepoint()
+.. method:: django.db.transaction.savepoint()
 
     Creates a new savepoint. This marks a point in the transaction that
     is known to be in a "good" state.
 
     Returns the savepoint ID (sid).
 
-.. method:: transaction.savepoint_commit(sid)
+.. method:: django.db.transaction.savepoint_commit(sid)
 
     Updates the savepoint to include any operations that have been performed
     since the savepoint was created, or since the last commit.
 
-.. method:: transaction.savepoint_rollback(sid)
+.. method:: django.db.transaction.savepoint_rollback(sid)
 
     Rolls the transaction back to the last point at which the savepoint was
     committed.