Actually no, too bad

README.rst

@@ -179,16 +179,14 @@ Configuration
   Set ``SOCIALACCOUNT_ADAPTER='allauth_ens.adapter.LongTermClipperAccountAdapter'``
   in `settings.py`
 
-
 Auto-signup
   Populated data
     - username: ``<clipper>@<entrance year>``
     - email: from LDAP's *mailRoutingAddress* field, or ``<clipper>@clipper.ens.fr``
     - first_name, last_name from LDAP's *cn* field
     - extra_data in SocialAccount instance, containing these field, plus *annee*
-  and *promotion* parsed from LDAP's *homeDirectory* field (available only on
-  first connection)
-
+and *promotion* parsed from LDAP's *homeDirectory* field (available only on
+first connection)
 
 Account deprecation
   At the beginning of each year (i.e. early November), to prevent clipper
@@ -198,7 +196,6 @@ Account deprecation
   (using LDAP), so that a known user keeps his account, but a newcomer won't
   inherit an archicube's.
 
-
 Customize
   You can customize the SocialAccountAdapter by inheriting
   ``allauth_ens.adapter.LongTermClipperAccountAdapter``. You might want to
@@ -209,7 +206,6 @@ Customize
   ``get_username`` (as done in the example website) allows to get rid of that
   behaviour, and for instance attribute a default entrance year.
 
-
 Initial migration
   If you used allauth without LongTermClipperAccountAdapter, or another CAS
   interface to log in, you need to update the Users to the new username policy,