4 ms·

I just use classes, so I'm not sure what you took my meaning to be. I'm certainly not requiring the singleton library.

• sophacles 16y ago
  A module is a singleton. No matter how many times you import foo, the namespace foo is always the same. If you reassign foo.bar in in code in module x, then later access foo.bar from module y, it will be the value assigned in X. This is not amenable to inheritance tho, however there is a strong argument against inheritance in singletons anyway. Further, the borg pattern is considered "more pythonic" in the case of inheritable singletons, as frequently what is desired in such cases is shared state vs instead of shared identity.
  • SlyShy 16y ago
    Thank you for explaining. :)
  • njharman 16y ago
    > No matter how many times you import foo Just don't reload it.
    • sophacles 16y ago
      Well, as far as I am concerned, if import foo is the same as instantiating foo, then reload is calling destructor then instantiation again. How is this worth comment? In a discussion of c++ singletons would you comment "Just dont call delete fooptr; fooptr = new foo();"?
    • mdg 16y ago
      from foo import bar
  • moe 16y ago
    If you reassign foo.bar in in code in module x, then later access foo.bar from module y, it will be the value assigned in X. In the general case, yes. Unfortunately, due to some quirks in the module loader, assigning bar right inside foo might not yield the expected result, though. This is actually one of the python warts that annoys me the most.