Pylint

-------------

- Removed usage of a Django object, as importing it caused Django to
try to configure itself and thus throw an ImproperlyConfigured
exception.

-----------

- `Issue 7 <https://github.com/PyCQA/pylint-django/issues/7>`__
Improved handling of Django model fields
- `Issue 10 <https://github.com/PyCQA/pylint-django/issues/10>`__ No
warning about missing **unicode** if the Django python3/2
compatability tools are used
- `Issue 11 <https://github.com/PyCQA/pylint-django/issues/11>`__
Improved handling of Django form fields
- `Issue 12 <https://github.com/PyCQA/pylint-django/issues/12>`__
Improved handling of Django ImageField and FileField objects
- `Issue 14 <https://github.com/PyCQA/pylint-django/issues/14>`__
Models which do not define **unicode** but whose parents do now have
a new error (W5103) instead of incorrectly warning about no
**unicode** being present.
- `Issue 21 <https://github.com/PyCQA/pylint-django/issues/21>`__
``ForeignKey`` and ``OneToOneField`` fields on models are replaced
with instance of the type they refer to in the AST, which allows
pylint to generate correct warnings about attributes they may or may
not have.

-----------

- Python3 is now supported
- ``__unicode__`` warning on models does not appear in Python3

-----------

- Pylint now recognises ``BaseForm`` as an ancestor of ``Form`` and
subclasses
- Improved ``Form`` support
- `Issue 2 <https://github.com/PyCQA/pylint-django/issues/2>`__ - a
subclass of a ``Model`` or ``Form`` also has warnings about a
``Meta`` class suppressed.
- `Issue 3 <https://github.com/PyCQA/pylint-django/issues/3>`__ -
``Form`` and ``ModelForm`` subclasses no longer warn about ``Meta``
classes.