Django-hvad

This release is a collection of fixes and improvements, some of which may introduce minor compatibility issues. Please make sure you fix any deprecation warnings before upgrading to avoid those issues.

**Python and Django versions supported:**
- Django 1.5 is no longer officially supported.
- Django 1.6 has reached its end of life, and support will be dropped in hvad 1.4.
- As a reminder, Django 1.4 is still supported, so supported versions for this release are: 1.4, 1.6, 1.7, 1.8.

**New Features:**
- Russian and Latvian translations are now included, thanks to Juris Malinens — 248.

**Compatibility Warnings:** deprecated features pending removal in 1.3 have been removed. Most notably:
- Calling `save()` on an invalid form now raises an assertion exception.
- Classes `TranslatableModelBase`, `TranslationFallbackManager`, `TranslatableBaseView` and method `TranslationManager.using_translations()` no longer exist.
- Deprecated view methods and context modifiers now raise an assertion exception.

**Fixes:**
- Lift Django restrictions on translated fields in `Meta.unique_together` and `Meta.index_together` — 252.
- Properly forward model validation methods to translation validation methods, so that model validation detects constraint violations on the translation as well. Fixes duplicate detection in admin for unique constraints on translations — 251.
- Detect name clash between translated and non-translated fields — 240.
- Validate that at least one translation is provided when deserializing objects in `TranslationsMixin` — 256.
- Fix handling of model edition from an admin popup in Django 1.7 and newer — 253.
- Generate proper ORM structures for fallbacks. Avoids table relabeling breaking queries, for instance when using `update()` or feeding a queryset to another queryset — 250.

**Fixes:**
- Properly handle `language_code` in `Meta.unique_together` and `Meta.index_together` — 244.

**Fixes:**
- Make passing the `model` argument to queryset's `__init__` optional. Still
allow it to be passed either as a positional or named argument — 241.

This is a feature release, to push REST framework support onto the main package.

**Python and Django versions supported:**
- Due to this version being released early, end of support for Django 1.5 has been postponed until next release.

**New features:**
- Support for Django REST framework is now included. It requires REST framework version 3.1 or newer — 220.

**Fixes:**
- Backwards compatibility issue in get_field implementation — 233.
- Admin no longer breaks on models using another `pk` field than `id` — 231.

**Python and Django versions supported:**
- hvad now supports Django 1.8.
- Django 1.5 has reached its end of life, and support will be dropped in hvad 1.2.
Note however that Django 1.4 will still be supported.

**New features:**
- It is now possible to use translated fields in the `unique_together` and `index_together` settings on models. They cannot be mixed in a single constraint though, as table-spanning indexes are not supported by SQL databases.
- The `annotate` method is now supported. Support is still basic for now: annotations may not access more than one level of relation.

**Compatibility warnings:**
- Internal module `hvad.fieldtranslator` was no longer used, and was incompatible with Django 1.8. It has been removed.
- Deprecated method `using_translations()` has been removed. It can be safely replaced by `language()`.
- Deprecated `TranslationFallbackManager` class has been removed. Please use manager's `untranslated()` method instead.
- Deprecated `TranslatableModelBase` metaclass has been removed. Since release 0.5, hvad does not trigger metaclass conflicts anymore – 188.
- Overriding the language in `QuerySet.get()` and `QuerySet.filter()` was deprecated in release 0.5, and has now been removed. Either use the `language()` method to set the correct language, or specify `language('all')` to filter manually through `get` and `filter` – 182.
- `TranslatableModel`'s Internal attribute `_shared_field_names` has been removed.

**Deprecation list:**
- Passing `unique_together` or `index_together` as a `meta` option on `TranslatedFields` is now deprecated and will be unsupported in release 1.3. Put them in the model's `Meta` instead, alongside normal fields.
- Calling `save()` on an invalid `TranslatableModelForm` is a bad practice and breaks on regular Django forms. This is now deprecated, and relevant checks will be removed in release 1.3. Please check the form is valid before saving it.
- Generic views in `hvad.views` have been refactored to follow Django generic view behaviors. As a result, several non-standard methods are now deprecated. Please replace them with their Django equivalents — check 225.