Pylint-django-forked

* [PR 27](https://github.com/landscapeio/pylint-django/pull/27) - better `ForeignKey` transforms, which now work when of the form `othermodule.ModelClass`. This also fixes a problem where an inferred type would be `_Yes` and pylint would fail
* [PR 28](https://github.com/landscapeio/pylint-django/pull/28) - better knowledge of `ManyToManyField` classes

* Improved resiliance to inference failure when Django types cannot be inferred (which can happen if Django is not on the system path

* [Issue 25](https://github.com/landscapeio/pylint-django/issues/25) Fixing cases where a module defines `get` as a method

* Fixed a problem where type inference could get into an infinite loop

* 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/landscapeio/pylint-django/issues/7)
Improved handling of Django model fields
* [Issue 10](https://github.com/landscapeio/pylint-django/issues/10)
No warning about missing __unicode__ if the Django python3/2 compatability tools are used
* [Issue 11](https://github.com/landscapeio/pylint-django/issues/11)
Improved handling of Django form fields
* [Issue 12](https://github.com/landscapeio/pylint-django/issues/12)
Improved handling of Django ImageField and FileField objects
* [Issue 14](https://github.com/landscapeio/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/landscapeio/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.