Some cleanup

[macro1]

After I saw the Landscape badge @dnozay added, I decided to see if we could get a few of the issues addressed.

One thing I did that I'm not sure about is explicitly adding object as a base for the manager and admin classes to ensure they are new-type classes.

[treyhunner]

This and the other object inheritance doesn't make sense to me. admin.ModelAdmin is a new-style class.

[treyhunner]

👍 except for the object inheritance I don't understand.

[macro1]

Landscape claimed they were old-object... I'll revert. Maybe it's a 2/3 thing.

[dnozay]

I think that for object classes, you can just ignore those until they are addressed upstream (I mean directly in django)

[macro1]

@dnozay as you can see from our code, we are using super() within those classes. Wouldn't that raise a TypeError if managers and model admins really are old-style objects? Looking at the Django code it seemed like they are dynamic objects constructed using type(), maybe that's why Landscape wasn't detecting it correctly.

[treyhunner]

@macro1 type makes a new style class

[dnozay]

this could be some issue in pylint_django that landscape.io uses.