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 attri
04.01.11 02:56, Guido van Rossum пише:
> That said, I am sure there are use cases for static property and class
> property -- I've run into them myself.
>
> An example use case for class property: in App Engine, we have a Model
> class (it's similar to Django's Model class). A model has a "kind"
>
03.01.11 23:09, K. Richard Pixley пише:
> There's a whole matrix of these and I'm wondering why the matrix is
> currently sparse rather than implementing them all. Or rather, why we
> can't stack them as:
>
> class foo(object):
> @classmethod
> @property
> def bar(cls, ...):
>
On Wed, Dec 16, 2020 at 12:16:46AM -, Paolo Lammens wrote:
> Old thread, pity it didn't get any traction. I second this.
It is a thread from 2011. Do you think people will remember what it is
about, or still have it in their inboxes?
At this point, you should start a new thread (and link b
On 12/16/20 1:31 AM, Serhiy Storchaka wrote:
Things like abstractclassmethod are legacy. It is more preferable to
combine elemental decorators.
I completely disagree, although I suppose the determining factor is one's point of view. I see it as
"abstractclassmethod" being its own thing, and
