title: Can't resolve Pylint 'too-many-instance-attributes'
body: <p>There seems to be something going on behind the scenes with the linter and a few of my classes. I have a few classes with too many (up to 26 in one case) instance attributes. One I was able to fix by grouping together some of the related attributes into new classes. However, this method isn't working for me on the latest class. All the attributes are primitives at the moment, and I can easily break them apart into related groups. The offending class follows:</p>
  
  <pre><code>class BigClass():
      """
      This class has too many (16/8) instance attributes!
      """
      a = float(0)
      b = float(0)
      c = float(0)
      d = float(0)
      e = float(0)
      f = float(0)
      g = float(0)
      h = float(0)
      i = float(0)
      j = float(0)
      k = float(0)
      l = float(0)
      m = float(0)
      n = float(0)
      o = float(0)
      p = float(0)
  </code></pre>
  
  <p>I then broke it up into two classes, grouping together appropriate attributes.</p>
  
  <pre><code>class SmallClass1():
      """
      This class is smaller, it has 8/8 attributes.
      It is a logical grouping of 8 attributes that were
      previously found in BigClass()
      """
      a = float(0)
      b = float(0)
      c = float(0)
      d = float(0)
      e = float(0)
      f = float(0)
      g = float(0)
      h = float(0)
  
  class SmallClass2():
      """
      This class is smaller, it has 8/8 attributes.
      It is a logical grouping of 8 attributes that were
      previously found in BigClass()
      """
      i = float(0)
      j = float(0)
      k = float(0)
      l = float(0)
      m = float(0)
      n = float(0)
      o = float(0)
      p = float(0)
  
  class NewBigClass():
      """
      This class still has too many (16/8) instance attributes!
      """
      grouping1 = SmallClass1()
      grouping2 = SmallClass2()
  </code></pre>
  
  <p>However, the linter is still claiming that there are too many attributes in the NewBigClass() declaration.
  Am I missing something, perhaps the core understanding of what this warning is trying to avoid?
  I'm not sure why I was able to solve this for one class, but not all of them. They all follow a similar layout.</p>
  
  <p>I appreciate any help.</p>