Add anti patterns sectiAdd “Anti-Patterns” section to README with explanations (#256)on (#459)

* added default return value in get_localizer to prevent KeyError

* cleaned up docstring formatting and removed unnecessary asterisks

* Add Anti-Patterns section explaining discouraged design patterns

Author: ABHIRANJAN-KUMAR1

README.md

@@ -120,3 +120,27 @@ You can also run `flake8` or `pytest` commands manually. Examples can be found i
 ## Contributing via issue triage [![Open Source Helpers](https://www.codetriage.com/faif/python-patterns/badges/users.svg)](https://www.codetriage.com/faif/python-patterns)
 
 You can triage issues and pull requests which may include reproducing bug reports or asking for vital information, such as version numbers or reproduction instructions. If you would like to start triaging issues, one easy way to get started is to [subscribe to python-patterns on CodeTriage](https://www.codetriage.com/faif/python-patterns).
+
+
+## 🚫 Anti-Patterns
+
+This section lists some common design patterns that are **not recommended** in Python and explains why.
+
+### 🧱 Singleton
+**Why not:**
+- Python modules are already singletons — every module is imported only once.
+- Explicit singleton classes add unnecessary complexity.
+- Better alternatives: use module-level variables or dependency injection.
+
+### 🌀 God Object
+**Why not:**
+- Centralizes too much logic in a single class.
+- Makes code harder to test and maintain.
+- Better alternative: split functionality into smaller, cohesive classes.
+
+### 🔁 Inheritance overuse
+**Why not:**
+- Deep inheritance trees make code brittle.
+- Prefer composition and delegation.
+- “Favor composition over inheritance.”
+

patterns/creational/builder.py

@@ -1,13 +1,12 @@
 """
-*What is this pattern about?
+What is this pattern about?
 It decouples the creation of a complex object and its representation,
 so that the same process can be reused to build objects from the same
 family.
 This is useful when you must separate the specification of an object
 from its actual representation (generally for abstraction).
 
-*What does this example do?
-
+What does this example do?
 The first example achieves this by using an abstract base
 class for a building, where the initializer (__init__ method) specifies the
 steps needed, and the concrete subclasses implement these steps.
@@ -22,16 +21,15 @@ class for a building, where the initializer (__init__ method) specifies the
 In general, in Python this won't be necessary, but a second example showing
 this kind of arrangement is also included.
 
-*Where is the pattern used practically?
-
-*References:
-https://sourcemaking.com/design_patterns/builder
+Where is the pattern used practically?
+See: https://sourcemaking.com/design_patterns/builder
 
-*TL;DR
+TL;DR
 Decouples the creation of a complex object and its representation.
 """
 
 
+
 # Abstract Building
 class Building:
     def __init__(self) -> None:

patterns/creational/factory.py

@@ -54,7 +54,8 @@ def get_localizer(language: str = "English") -> Localizer:
         "Greek": GreekLocalizer,
     }
 
-    return localizers[language]()
+        return localizers.get(language, EnglishLocalizer)()
+
 
 
 def main():