The Singleton Pattern: Single-Instance Architecture
The Singleton pattern ensures a class has only one instance and provides a global access point to it. Overriding `__new__` enforces single instance creation 🏛️.
class DatabaseConnection:
_instance = None
def __new__(cls):
if cls._instance is None:
cls._instance = super().__new__(cls)
cls._instance.connected = True
return cls._instance
db1 = DatabaseConnection()
db2 = DatabaseConnection()
print(f"db1 is db2: {db1 is db2} 🏛️")
# 116. The Singleton Pattern: Single-Instance Architecture The Singleton pattern ensures a class has only one instance and provides a global access point to it. Overriding `__new__` enforces single instance creation 🏛️. ```python class DatabaseConnection: _instance = None def __new__(cls): if cls._instance is None: cls._instance = super().__new__(cls) cls._instance.connected = True return cls._instance db1 = DatabaseConnection() db2 = DatabaseConnection() print(f"db1 is db2: {db1 is db2} 🏛️") ``` In Python, module-level variables are naturally singletons because `import` caches modules in `sys.modules`. Prefer modules over complex singleton classes when possible! 🏛️ --- ### Question Which dunder method must be overridden to intercept and control object instance allocation for a Singleton? 🧠 - [ ] a. `__new__` 🏛️ - [ ] b. `__init__` - [ ] c. `__call__` - [ ] d. `__repr__` --- ### Challenge Write class `ConfigManager` implementing Singleton via `__new__`. Instantiate `c1 = ConfigManager()`, `c2 = ConfigManager()`. Print `c1 is c2`. 🎯 <details> <summary>Solution</summary> ```python class ConfigManager: _instance = None def __new__(cls): if cls._instance is None: cls._instance = super().__new__(cls) return cls._instance c1 = ConfigManager() c2 = ConfigManager() print(c1 is c2) ``` </details>