Message173200
| Author |
asvetlov |
| 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月17日.20:00:19 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1350504019.31.0.158204375182.issue16267@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
After brief looking sources I figured out it can be solved by adding setters for __isabstractmethod__ to classmethod/staticmethod objects.
It can be done, I'll try to make a patch.
For property situation is worse: property is abstract if any of getter/setter/deleter is abstract.
Which object attribute should be set for setting __isabstractmethod__ for property?
We can make the rule: abstractmethod for classmethod/staticmethod/property should set descriptor as abstract, not functions behind it.
I'm not sure is it true solution but I like to try to make a patch for that.
Anyway, the patch for describing current behavior in the docs is welcome. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年10月17日 20:00:19 | asvetlov | set | recipients:
+ asvetlov, ncoghlan, benjamin.peterson, stutzbach, eric.araujo, Arfrever, r.david.murray, daniel.urban, christopherthemagnificent, docs@python, dsdale24, python-dev, eric.snow, Darren.Dale |
| 2012年10月17日 20:00:19 | asvetlov | set | messageid: <1350504019.31.0.158204375182.issue16267@psf.upfronthosting.co.za> |
| 2012年10月17日 20:00:19 | asvetlov | link | issue16267 messages |
| 2012年10月17日 20:00:19 | asvetlov | create |
|