@staticmethod vs module-level function
<p>This is not about <code>@staticmethod</code> and <code>@classmethod</code>!  I know how <code>staticmethod</code> works.  What I want to know is the proper use cases for <code>@staticmethod</code> vs. a module-level function.</p>

<p>I've googled this question, and it seems there's some general agreement that module-level functions are preferred over static methods because it's more pythonic.  Static methods have the advantage of being bound to its class, which may make sense if only that class uses it.  However, in Python functionality is usually organized by module not class, so usually making it a module function makes sense too.  </p>

<p>Static methods can also be overridden by subclasses, which is an advantage or disadvantage depending on how you look at it.  Although, static methods are usually "functionally pure" so overriding it may not be smart, but it may be convenient sometimes (though this may be one of those "convenient, but NEVER DO IT" kind of things only experience can teach you).</p>

<p>Are there any general rule-of-thumbs for using either staticmethod or module-level functions?  What concrete advantages or disadvantages do they have (e.g. future extension, external extension, readability)?  If possible, also provide a case example.</p>
