This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author fov
Recipients Claudiu.Popa, berker.peksag, fov, kevinbenton, lukasz.langa, michael.foord
Date 2015-06-02.16:27:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Regarding Claudiu's comment about `staticmethod(x)` or `classmethod(x)` not being callable, would it suffice to add a specific check of the form `(isinstance(x, (classmethod, staticmethod)) and _callable(x.__func__))`?

Separately, would it be better to include the check for `staticmethod` and `classmethod` objects (with an underlying callable) inside the `_callable` function? Not sure if this would break anything, but it seems like conceptually the issue is with the definition of a callable object, not the selection of mock type to use.
Date User Action Args
2015-06-02 16:27:05fovsetrecipients: + fov, michael.foord, Claudiu.Popa, lukasz.langa, berker.peksag, kevinbenton
2015-06-02 16:27:05fovsetmessageid: <>
2015-06-02 16:27:05fovlinkissue23078 messages
2015-06-02 16:27:05fovcreate