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 eric.snow
Recipients Arfrever, Darren.Dale, asvetlov, benjamin.peterson, christopherthemagnificent, daniel.urban, docs@python, dsdale24, eric.araujo, eric.snow, ncoghlan, python-dev, r.david.murray, stutzbach
Date 2012-10-18.15:54:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1350575680.22.0.270140249435.issue16267@psf.upfronthosting.co.za>
In-reply-to
Content
The catch is that when abstractmethod is the inner decorator, __isabstractmethod__ is set on the object that classmethod/staticmethod is wrapping.  When abstractmethod is the outer decorator, __isabstractmethod__ is set on the resulting classmethod/staticmethod object instead.  Unless there is some practical reason that the distinction matters, I'm +1 on letting __isabstractmethod__ be set on classmethods and staticmethods.
History
Date User Action Args
2012-10-18 15:54:40eric.snowsetrecipients: + eric.snow, ncoghlan, benjamin.peterson, stutzbach, eric.araujo, Arfrever, r.david.murray, asvetlov, daniel.urban, christopherthemagnificent, docs@python, dsdale24, python-dev, Darren.Dale
2012-10-18 15:54:40eric.snowsetmessageid: <1350575680.22.0.270140249435.issue16267@psf.upfronthosting.co.za>
2012-10-18 15:54:40eric.snowlinkissue16267 messages
2012-10-18 15:54:40eric.snowcreate