The procedural views were deprecated in Django 1.11 and will be removed in Django 2.1.

Fixes #2547.

Notification subjects have a max length of 255 characters, which can easily be exceeded by long product names. Change the alert logic to provide a short notification subject and put the longer content in the notification body.

This patch also modifies the notification utils to make it obvious that the positional argument is a notification subject, not a body.

This is to prevent the possibility of spamming a user by generating lots of alert confirmation emails for product alerts.

Also allow unconfirmed alerts to be cancelled - we send a cancellation link in the confirmation email, so we should let users cancel an alert if they don't want to confirm it.

Fixes #2401.

Better to use filenames which are commonly used in the python word then
custom ones.

Latter one is deprecated

We only needed it because Django 1.4 shipped with a pretty old version
of six. Support for that has been removed, and Django 1.5 ships with six
1.6.1, which is more current than we required.

This nicely avoids an issue with django-extra-views pinning a six
version which caused the sandbox build to fail:
https://travis-ci.org/tangentlabs/django-oscar/jobs/32223978#L971

The former throws a deprecation warning and causes the test suite to
fail.

Most email servers don't respect capitalisation, and many users don't
know about it. So Oscar now does what the rest of the world does, and
ignores the capitalisation when looking up an email address.

Fixes #1179.

The new version has been extended to allow the success URLs and messages
to be easily customised.

We also now redirect staff members to the dashboard when they first
login.

Before this change, it was conflating WebTest functionality with the
Django test client. This change removes the Django test client
functionality (namely, the login function which was being automatically
called).

A shed-load of tests are adjusted to work with this change.

This almost completes the work for #826 - only a couple more references
to the Django client are left in the test codebase.

Previously, the 'key' kwarg was not respected and all products would get
added to the first wishlist.

Thanks to @DanielChu for reporting, and supplying a fix.
Fixes #1216

During the registration and in dashboard, the new password is required
to have min 6 characters and not be in common passwords. Those rules are
not enforced when changing password in the account section or resetting
password.

Extract password validators into core validators as they are used by
multiple apps. `password_validators` now contains all validators applied
to passwords: DRY principle.

Changed auth tests to have a proper password for password reset.

This should always be used instead of Django's silent version.

Previously, the test suite ran with a custom user model for Django >=
1.5, but it didn't subclass Oscar's AbstractUser.  This commit adjusts
the custom user model to subclass Oscar's so we can test functionality
within the custom user class.

This does require a change to the way tests authenticate as we don't
actually use the username field.

We add a new form to the profile section that requires the customer to
confirm their password, but which then deletes their user.

ClientTestCase is deprecated.

Fixes #826
Fixes #1007

Analogous to the settings for the basket cookie, the cookie that stores
the recently viewed products is now configurable.

Fixes #1064

Simplify implementation.

The locations of the form to re-order an order has changed, so the tests
needed updating.

This was a code change introduced in the refactoring, but does not make
any sense. Luckily, it also caused the tests to fail, so I'm happy to
revert it.

- Use a FormView (as it is a form view)
- Move the redirect URL validation into the form