Guido van Rossum wrote:
> Yes, this whole thing is deeply about readability. It *started* with
> the observation that the post-function-body decorator "syntax" had
> usability / readability issues. A lot of Python is about that.
I agree. In fact, I've been convinced by both sides that both
@decorators and list-after-def solutions have major readability
drawbacks. For example, this is more readable than both:
decorate classmethod:
def foo(arg1,arg2):
...
But it is less usable when the decorator applies to a single function,
unless a syntax is allowed to do it without indentation. And there's a
new keyword. But adding a special character to avoid adding a new
keyword? Wouldn't a "from __future__ import decorate" until Python 2.X
or 3 be better? It seems like a good compromise to me...
Regards,
Nicolas
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