Take the 2-minute tour ×  I would very much like to integrate
pylint into the build process for my python projects, but I have
run into one show-stopper: One of the error types that I find
extremely useful--:E1101: *%s %r has no %r member*--constantly
reports errors when using common django fields, for example:
E1101:125:get_user_tags: Class 'Tag' has no 'objects' member
which is caused by this code:  def get_user_tags(username):
Gets all the tags that username has used.     Returns a query
set.    return Tag.objects.filter(  ## This line triggers the
error.  # Here is the Tag class, models.Model is provided by
Django: class Tag(models.Model):    Model for user-defined
strings that help categorize Events on    on a per-user basis.
name = models.CharField(max_length=500, null=False, unique=True)
def __unicode__(self):        return self.name  How can I tune
Pylint to properly take fields such as objects into account?
(I've also looked into the Django source, and I have been unable
to find the imple