- Jun 18, 2015
-
-
carlio authored
-
carlio authored
-
carlio authored
-
carlio authored
-
Sebastien Mirolo authored
-
carlio authored
-
carlio authored
-
Carl Crowder authored
Add support for more rest_framework classes, and django_filters
-
- May 26, 2015
-
-
Michael Bertolacci authored
-
- Apr 20, 2015
-
-
Carl Crowder authored
added support for Django REST Framework
-
Carl Crowder authored
Ensure pylint doesn't raise an error on 'raise SomeModel.DoesNotExist'
-
Mike Bryant authored
Fixes #46
-
- Apr 04, 2015
-
-
Luis Rodrigues authored
-
- Jan 31, 2015
- Jan 29, 2015
- Jan 24, 2015
-
-
carlio authored
Using "sudo: false" to use the shiny Docker container version of travis CI (see http://docs.travis-ci.com/user/workers/container-based-infrastructure/)
-
carlio authored
[refs #37 #40] Fix the infinite loop problem using an inference tip to infer that fields are both their original subclass and also a type shim representing them at runtime. Also, supresses R0903 (too few methods) from models and views, which started happening recently
-
carlio authored
-
carlio authored
-
carlio authored
-
carlio authored
[refs #37] As of astroid 1.3.3, class method resolution order is taken into consideration: https://bitbucket.org/logilab/astroid/commits/b1d8107715a4ceeeeb3f4a9065b67817e8cdc643 This caused an infinite loop when using pylint-django, as the model and form field transforms extended the base Django object then replaced it. This caused the MRO lookup to find a class as its own ancestor. The model and form field transforms have been simplified, so that instead of building a module and replacing each class individually, instead, the correct "dummy" parent class is simply appended. This means that the original parent node (eg, CharField) is not replaced by itself. This also has the side effect of no longer confusing pylint when it comes to __init__/__new__ differences for field classes which extend "immutable" base classes as a result of this transform.
-
- Nov 05, 2014
-
-
Damien Nozay authored
... subclasses. This is done by exposing a Manager object. see https://github.com/treyhunner/django-simple-history/pull/134 as well.
-
- Oct 06, 2014