Python Design Patterns 1
summary
Argues that many Gang of Four patterns either shrink or move into Python itself: examples include using dict.get default instead of manual lookups, duck typing replacing explicit interfaces, and CPython reusing small integers; some patterns live in the stdlib or libraries like the socket.makefile adapter and lxml’s builder, while the iterator protocol becomes language syntax. Claims three reasons: language features, frameworks providing patterns, and most Python projects being small scripts or web request handlers so heavy architectural patterns rarely appear.
AI-written summary · about
chapters (4)
related talks
29mYou Don't Need That!
25mDesign Patterns Unleashed: Building Elegant and Confident Solutions
57mDesign Patterns in Dynamic and Functional Languages
50mThe Clean Architecture in Python
43mPlain Pattern Language
31mGuardrails: An Alternative View of Safely Working in Python
43mDesign Patterns - The Most Common Misconceptions (1 of N)
04mOn the shoulders of giants