title: Pylint complains "no value for argument 'cls'"
body: <p>I have defined the following class-method to define my object from a pandas.DataFrame instead of from a list like so:</p>
  
  <pre><code>class Container(object):
      @classmethod
      def from_df(cls, df):
          rows = [i for _, i in df.iterrows()]
          return cls(rows)
  </code></pre>
  
  <p>and <code>pylint</code> complains at the <code>return</code> line with the E1120 'code-smell':</p>
  
  <blockquote>
    <p>No value for argument 'cls' in constructor call</p>
  </blockquote>
  
  <p>I can't see anything wrong with it, and it seems to work. Does anybody else maybe have an idea what could be wrong with it?</p>
  
  <p><strong>Update</strong>: Ugh, user <code>rogalski</code> got it (I think): I confused myself by using the same variable name for a class that comes in as argument:</p>
  
  <pre><code>def __init__(self, iterable, cls):
      self.content = [cls(item) for item in iterable]
  </code></pre>
  
  <p>I do this because I have different kind of objects coming in and this Container class is the abstract version of this daughter:</p>
  
  <pre><code>class FanContainer(Container):
      def __init__(self, iterable):
          super().__init__(iterable, Fan)
  </code></pre>
  
  <p>with <code>Fan</code> being one of several classes that need to be 'contained'.
  Rogalski, want to write up an answer along the lines of saying that the error might reference a name of the <code>__init__</code> constructor? Cheers! (Now I have to dig why my code isn't stumbling over this...)</p>
  
  <p><strong>Update2</strong>
  Only realizing know how feeble I have coded this: I am using this basically like so:</p>
  
  <pre><code>fancontainer = FanContainer.from_df(df)
  </code></pre>
  
  <p>and because I am overwriting the <code>__init__</code> in the <code>FanContainer</code> class, I guess that's why my code still worked? So, the abstract <code>__init__</code> is never being called directly, because I never call <code>Container.from_df(df)</code> but only the daughter classes' classmethods. Guess that can be done prettier a different way.</p>