Guido van Rossum wrote: > IIUC Thomas found that this breaks some current use of staticmethod. I*I*UC, it wasn't making it callable that was the problem, it was changing the behaviour so that the staticmethod wrapper returns itself instead of the underlying object when accessed as a descriptor. The reason for doing *that* appears to be so that you can transplant a staticmethod-wrapped object from one class to another without surprises. But is that really a common enough thing to do that it warrants special attention? Would it be so bad to require applying staticmethod() again in such a situation? -- Greg
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