It makes it easy to mark a method deprecated and is easy to look up
deprecated methods via grep (look for '@deprecated').

These are simpler as they are guaranteed to have an email field which
Oscar uses for authentication.

Django 1.5 makes it optional, but given our Emailbackend being default,
that seems like the sensible way to deal with it.

ExtendedURLValidator does not pass down verify_exist in it's __init__
method. But as it's super class URLValidator then sets self.verify_exists to
False, any passed value was ignored.

This is required to allow the pages component of the dashboard to
continue to work correctly.

* Tidy implementation of validator
* Tests improved and moved to tests/integration (as they call resolve
  internally)

Introduces the concept of a "feature" that can be hidden. A list of
features to hide can be supplied in OSCAR_HIDDEN_FEATURES.

Feature hiding is currently supported in two places.
Application instances can carry a "hidable_feature_name". If set and
found in OSCAR_HIDDEN_FEATURES, post_process_urls will return an empty
set of url patterns, hence disabling relevant views.
display_tags also has a new template block tag iffeature.
{% iffeature "feature" %}xxx{% endiffeature %} will hide everything
inside the block if the feature is hidden.

Fixes #614

You only want to compile Less files if you are developing the CSS of
Oscar.  Most people don't do this and so we default to serving
compressed CSS without Less compilation.  This also means that
the many contributors don't need to bother installing node.js and lessc,
which makes the installation process much simpler.

This change also re-introduces the `USE_LESS` setting which controls
whether Less files are used or not.

So stopwords can be moved from slugs

This uses the unidecode package to convert non-ASCII words to ASCII
equivalents.  We use a new slugify function to wrap this logic as we
will want to use it elsewhere.

See this StackOverflow thread for context:
http://stackoverflow.com/questions/702337/how-to-make-django-slugify-work-properly-with-unicode-strings/

Unidecode becomes a new dependency for Oscar.
https://pypi.python.org/pypi/Unidecode

Hat-tip to @avsazonov for suggesting this fix.

This involves some changes to the template block structure to make it
easy to compress the correct files.

* A new block cdn_scripts has been introduced as CDN-loaded scripts
  can't be compressed.
* A new setting 'USE_LESS' controls whether to use the LESS-generated
  files or the compressed files (which will need to be generated
  manually as they aren't in source control).
* A fallback for jQuery UI is added
* The CSS block was renamed to be clearer
* The bootstrap CSS was brought out of the LESS file into the page.
  This makes it easier to compress.

This helps with views that can return a AJAX response.  We store the
messages temporarily then apply them to the request, or serialise to
JSON at the end.

Also split them into unit and functional tests.

It handles the situation where there is no profile model too, and
dyncamically builds a profile and user form

segments.

To make it trivial to change the logo and branding without forking
templates.

model from within forms.validators

I added a new validator to oscar.core.validators that validates
absolute and relative URL and checks if the URL already exists. We
use this functionality when creating flatpages in the dashboard to
check if the URL can be used.
The validation includes *two* calls to ExtendedURLValidator to
validate the URL in the first run and then check if it already
exists in the second. This might not be the most efficient way
of handling it. The reason to do it that way is that it reduces
the amount of code that has to be replicated.

This ones won't causes pep8 to complain.