> I'm very happy with the design for type-class unification -- it looks > like an excellent move towards making Python more consistent and flexible. Thanks! > However, the mechanism for declaring class and static methods: > > class MyClass: > def method(x, y): # part 1 > ... > > method = staticmethod(method) # part 2 > > ...sticks out as awkward and strange to read. Kevin Smith and Paul > Prescod commented earlier on this, and i agree with their opinion that > a more direct declaration would be a better way to do this. Understood, and agreed. It is my plan to eventually provide syntax for this. However, right now I need to concentrate on getting the underlying mechanisms to work. The unification is a lot of work, and I'd like to finish the run-time before I start thinking about syntactic sugar. I can't promise that I'll change the syntax before 2.2 is released -- there will be plenty of time after that, and there are plenty of more important things to do before I can make the release. --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