Django-lazysignup

-------

This release introduces the following backwards-incompatible changes:

* A test project was added to make running the tests a little easier. The old
way of running the tests has been removed.
* The `urls.py` no longer hardcodes `convert` as the URL prefix (thanks
to mitar)

-------

This is a bugfix and feature release. The internal API has changed to no
longer depend on session keys for username generation. This should be
backwards-compatible as long as you are using the documented API.

The following bugs have been fixed:

* PEP8 cleanups
* Tweak setup.py to make sure templates are installed (thanks Kurt Grandis)

The following features have been added:

* Removed the hard dependency on session keys to generate usernames, as it was
unnecessary.
* remove_expired_users should no longer depend on using the database session
backend - it will instead use SESSION_COOKIE_AGE to find lazy users
who have not logged in recently and whose sessions will therefore have
expired.

You should still not use remove_expired_users without reviewing the code;
in particular, you may wish to subclass the command and override
`to_delete()`.

These changes are somewhat experimental, so this is a beta release - it is
*not* recommended that you run this in production. Testing and feedback is
welcome.

-----

This is a feature release. Custom user classes are now supported via the
``LAZYSIGNUP_USER_MODEL`` setting. This is a backwards-compatible change.

Thanks to Luke Zapart for the idea and initial implementation.

-----

This is a bugfix release. Issues fixed:

* The LazySignupBackend no longer relies on a specific User class to
authenticate a user. It now uses the fact that there is a relationship
between the LazyUser and the main site User class. This fixes the bug
where authenticate() was looking directly for UNUSABLE_PASSWORD, and also
paves the way for custom user classes.

-----

This is a bugfix release. Issues fixed:

* https://github.com/danfairs/django-lazysignup/issues#issue/2 - Invalid user
IDs in the session could cause an AttributeError from the auth backend.

Thanks to Alex Ehlke for the report and patch.

-----

This is a feature release:

* Users created lazily but not currently logged-in are now correctly detected
as lazy users. To facilitate this, a ``LazyUser`` model is included. Note
that existing code using ``is_lazy_user`` only on authenticated users will
continue to work, as the old method of checking the ``backend`` attribute
of the ``User`` object has been retained - it's faster to do that than a
potentially unnecessary database query.

For those who use it, a South migration is provided to create the initial
table. Data migration will be handled by South migrations from now on.

* The canonical import location of ``is_lazy_user`` has changed from within
``lazysignup.templatetags.lazysignup_tags`` to ``lazysignup.utils``.
Existing code that imports from the old location will continue to work.