Requirements: bump required minimum Django version
Cleanup: Just get the template loader class and instantiate it.

This avoids us problems when moving to Django 1.5 which lacks that private
instance of the loader.
Profiles: Apply PR to get rid of function-based generic views

The PR is in https://bitbucket.org/ubernostrum/django-profiles/pull-request/6/

There is another PR with a slightly different approach, but when and if
django-profiles finally supports class-based generic views the code will be
quite similar to any of these two PRs.

Whitespace changes are not merged to make it easier to see the real changes.

This commit and the previous two ones fix bug #2517
Cleanup: django.conf.urls.defaults is deprecated

Use django.conf.urls instead.

This makes 'profiles' app to be less aligned with upstream code, but it is
necessary for making this work on new Django releases.
pootle_profile: Use reverse() instead of hardcoded urls
Cleanup: align with our styling
pootle_profile: Move profile URLs to /profiles/

/accounts/ is reserved for accounts (authentication) related urls
Django 1.5: Use class-based TemplateView

The function-based `direct_to_template()` was removed in Django 1.5.
initdb: Do not create a manual transaction for projects/languages/admin

This makes Django 1.6 complain as sqlite will not play nice with manual
transactions outside atomic blocks
Django 1.5: removed `{% load url from future %}` calls

No need to keep these around since the behavior it brought is the default
in Django 1.5+.

Fixes #183.
Django 1.6: specified name in authentication URL patterns

Note that some names need to match those used in
django.contrib.auth.views.

Fixes #179.
Django 1.5: used the receiver decorator

Mostly syntactic sugar to allow connecting various signals to the same
handler. Other signal handlers have been left intact.

Fixes #176.
Django 1.6: renamed `get_query_set()` to `get_queryset()`

Fixes #181.
Profiles: fixed URLs
Django 1.6: don't use `print` in management commands

The statements have been replaced by `self.stdout.write()` calls.

Fixes #175.
Django 1.5: killed djblets

This old bundled dependency contained code incompatible with Django 1.5,
but apart from that the feature the code was depending on (keeping track
of site's title and build versions) is of no use for us anymore.

The commit moves the site's title straight away into the settings, so it
should be configured right there.

On the other hand the upgrade machinery has been taken out, as it's of no
pratical use for us. Our releases just depend on DB schema and data
migrations.

Fixes #177.
Settings: Specify ATOMIC_REQUESTS for DATABASES

Django 1.6 replaces TransactionMiddleware by ATOMIC_REQUESTS == True.
This allows more control over the transactions, however it also means
database backends that don't behave properly without autocommit will
break in 1.6 (such as sqlite).
Django 1.6: switch to atomic transactions

`transaction.atomic()` is the replacement for the legacy `autocommit()`,
`commit_on_success()` and `commit_manually()`.

Also dropped the `TransactionMiddleware`, which is replaced by the
`ATOMIC_REQUESTS` setting.

Fixes #180.
Django 1.6: be explicit about the fields included in ModelForms

Fixes #182.
Django 1.6: removed the depth attribute from `select_related()`

This is only to ensure compatibility with newer Django versions, and the
change mimics the behavior of the old `RelatedManager` most of the time.
In order to ensure the best performance, every manager should need to be
reviewed in a case-by-case basis.

Fixes #178.