From: "Guido van Rossum" <guido@python.org> > > However this could work: > > > > class Foo(object): > > myprop = property: > > """A computed property on Foo objects.""" > > def __get__(self): > > return ... > > def __set__(self, value): > > ... > > def __delete__(self): > > ... > > > > This would call property() with the results of parsing the indented block. > > Not sure yet this is a good idea, but it could have many other (possibly > > good, possibly harmful) uses. > > Funny, I had a vision of something very similar this morning in the > shower. :-) > > The problem is that this is a *very* radical change to the grammar, > and I'm not sure I can rigorously define how the switch from > "expression parsing mode" to "block parsing mode" should work. I would have thought that such a syntax is better left reserved to some hypothetical pep for anonymous blocks (extending lambdas, not that I personally favor/long for them) and not for something along the line of class in terms of synthetizing an object out of a by a block populated namespace. regards.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4