>> I think this use case is rather elegant: >> >> def singleton(cls): >> return cls() >> >> class Foo [singleton]: >> ... Guido> And how would this be better than Guido> class Foo(singleton): Guido> ... Guido> (with a suitable definition of singleton, which could just be Guido> 'object' AFAICT from your example)? "Better"? I don't know. Certainly different. In the former, Foo gets bound to a class instance. In the latter, it would be a separate step which you omitted: class Foo(singleton): ... Foo = Foo() Skip
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