- Pylint 1.4 dropped support for Python 2.6, therefore a constraint is added that pylint-django will only work with Python2.6 if pylint<=1.3 is installed
- #40 - pylint 1.4 warned about View and Model classes not having enough public methods; this is suppressed
- #37 - fixed an infinite loop when using astroid 1.3.3+
- #36 - no longer warning about lack of
__unicode__method on abstract model classes - PR #34 - prevent warning about use of
super()on ModelManager classes
- PR #27 - better
ForeignKeytransforms, which now work when of the formothermodule.ModelClass. This also fixes a problem where an inferred type would be_Yesand pylint would fail - PR #28 - better knowledge of
ManyToManyFieldclasses
- Improved resiliance to inference failure when Django types cannot be inferred (which can happen if Django is not on the system path
- Issue #25 Fixing cases where a module defines
getas 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 Improved handling of Django model fields
- Issue #10 No warning about missing unicode if the Django python3/2 compatability tools are used
- Issue #11 Improved handling of Django form fields
- Issue #12 Improved handling of Django ImageField and FileField objects
- Issue #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
ForeignKeyandOneToOneFieldfields 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
BaseFormas an ancestor ofFormand subclasses - Improved
Formsupport