Peter Sagerson  committed a21ae31

Version 1.1

With a few documentation fixes.

  • Participants
  • Parent commits 60df8d3

Comments (0)

Files changed (4)

File django_auth_ldap/

-version = (1, 0, 19)
-version_string = "1.0.19"
+version = (1, 1, 0)
+version_string = "1.1.0"

File docs/

 # built documents.
 # The short X.Y version.
-version = '1.0'
+version = '1.1'
 # The full version, including alpha/beta/rc tags.
-release = '1.0.19'
+release = '1.1'
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

File docs/index.rst

+Version 1.1 of django-auth-ldap is tested with Django 1.3 and 1.4. Earlier
+versions may still work, but they are not supported.
 Configuring basic authentication
 anonymously, you can set :ref:`AUTH_LDAP_BIND_DN` to the distinguished name of
 an authorized user and :ref:`AUTH_LDAP_BIND_PASSWORD` to the password.
-If you need to search in more than one place for a user, you can use
+(New in 1.1) If you need to search in more than one place for a user, you can use
 :class:`~django_auth_ldap.config.LDAPSearchUnion`.  This takes multiple
 LDAPSearch objects and returns the union of the results. The precedence of the
 underlying searches is unspecified.
 Multiple LDAP Configs
+(New in 1.1)
 You've probably noticed that all of the settings for this backend have the
 prefix AUTH_LDAP\_. This is the default, but it can be customized by subclasses
 of :class:`~django_auth_ldap.backend.LDAPBackend`. The main reason you would
 .. class:: LDAPSearchUnion
+    (New in 1.1)
     .. method:: __init__(\*searches)
         * ``searches``: Zero or more LDAPSearch objects. The result of the
-    version="1.0.19",
+    version="1.1",
     description="Django LDAP authentication backend",