Is anybody seriously trying to come up with a single alternative decorator proposal that most folks "out there" can support, to be presented to me (with implementation, please!) in time for 2.4b1? The endless repetition of old proposals on the one hand, and the outrageous overgeneralizations being proposed on the other hand, make me wonder if @decorator is going to win by default -- because nobody can agree on a better proposal. Which is fine with me, but let it be clear that if that happens, the community has itself to blame (or to thank, depending on which syntax you favor :-). The ipython and Leo authors have already said that their tools will survive @decorators. --Guido van Rossum (home page: http://www.python.org/~guido/)
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