A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2004-March/043468.html below:

[Python-Dev] PEP 318 - posting draft

[Python-Dev] PEP 318 - posting draft [Python-Dev] PEP 318 - posting draftSkip Montanaro skip at pobox.com
Wed Mar 24 11:21:57 EST 2004
    >> 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


More information about the Python-Dev mailing list

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