[refs #15] There never was any version-specific code, so it is (currently) better just to remove the version-based loading, meaning new versions of Django will not create a warning when pylint-django is used
Merge branch 'master' into develop
[refs #7] Adding a whole bunch of additional transformations for Django fields based on the idea of @jproffitt - they all now extend both the Django field (for constructor use and direct manipulation and usage) as well as a type which accurately reflects what they are transformed into by the model meta-programming
ManyToManyField is now a QuerySet, which it is effectively is normal use. This removes most problems of many-to-many fields not having count() or exclude() methods and similar
[refs #11] Using the same technique as #7 (thanks again @jproffitt!) form fields should now have the behaviour both of the parent Django Field type as well as the more fundamental type they represent
[refs #12] Improving the type handling of FileField and ImageField files using a similar technique to #7 and the solution suggested by @enoren in #12 - namely, subclass both the Django Field type and the type that it is converted to by Django meta-programming
Merging from GitHub develop
[refs #14] __unicode__ warnings for models which do not declare them are now more nuanced: if a parent declares __unicode__ then the warning code will be W5103 instead of W5101, allowing people finer grained control of whether they want that error message or not