Old thread, pity it didn't get any traction. I second this.
Except perhaps the @staticproperty: since a static (method|property) is bound to neither the instance nor the class, it doesn't seem straightforward/intuitive as to where the value set in the setter should go. E.g. if it sets an attribute in the class that defined the @staticproperty, then that class' attribute could be modified through a subclass or a subclass' instance by doing `obj.prop = value` which seems like too much of "spooky action at a distance` (since a static attribute is by definition bound to the class and only the identical class, not any subclasses or instances). _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/CAXGNUCHCNBLCZM4IVTMCDU6DFYZFDCW/ Code of Conduct: http://python.org/psf/codeofconduct/
