"Phillip J. Eby" <pje at telecommunity.com> writes: > +classmethod > +attrs(spam="fidget") > def foo(...): > ... > > [classmethod(), attrs(spam="fidget")] > def foo(...): > ... > > ~classmethod > ~attrs(spam="fidget") > def foo(...): > ... > > -classmethod > -attrs(spam="fidget") > def foo(...): > ... > > All of these are possible, and each likely to have *some* > proponents. Oh, and let's not forget the question of application > order of the decorations. :) I personally favor a(b(c(...))) > ordering for decorations that are listed before the 'def', even > though I favor a(), b(), c() ordering for decorations that come > after. I don't think any of these syntaxes allow classmethod to remain what it is, a "regular" function... not that I consider it a prerequisite or anything. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
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