Learning Python Design Patterns

by Gennadiy Zlobin

Design pattern is a well-known approach to solve some specific problems which each software developer comes across during his work. Design patterns capture higher-level constructs that commonly appear in programs. If you know how to implement the design pattern in one language, typically you will be able to port and use it in another object-oriented programming language.

The choice of implementation language affects the use of design patterns. Naturally, some languages are more applicable for certain tasks than others. Each language has its own set of strengths and weaknesses. In this book, we introduce some of the better known design patterns in Python. You will learn when and how to use the design patterns, and implement a real-world example which you can run and examine by yourself.

You will start with one of the most popular software architecture patterns which is the Model- View-Controller pattern. Then you will move on to learn about two creational design patterns which are Singleton and Factory, and two structural patterns which are Facade and Proxy. Finally, the book also explains three behavioural patterns which are Command, Observer, and Template.

Approach

This book takes a tutorial-based and user-friendly approach to covering Python design patterns. Its concise presentation means that in a short space of time, you will get a good introduction to various design patterns.

Who this book is for

If you are an intermediate level Python user, this book is for you. Prior knowledge of Python programming is essential. Some knowledge of UML is also required to understand the UML diagrams which are used to describe some design patterns.

Genres: Programming, Nonfiction, Computer Science

100 pages, Paperback

First published January 1, 2013

Reviews

[Uriel Vidal]

Explica muy bien los patrones de diseño, me gustó mucho que generará el UML del patrón y a través de él generará los ejemplos, además el capítulo de los antipatrones es muy bueno ya que hace nos muestra las dos caras de la moneda de los modelos que se usan en software.
Los puntos a que se pueden mejorar del libro son la forma en que explica los primeros patrones, ya que parecieran que no entran en la misma estructura de los demás, es decir, el las últimas explicaciones un modelo explicativo:
Descripción del patrón -> UML -> ejemplo -> variaciones -> anexos (como FAQ o cosas a tomar en cuenta)
Pero en los primeros capítulos cambia el modo explicativo y después de la descripción:
Descripción del patrón -> variaciones -> UML -> ejemplo -> anexos
Este cambió, aunque mínimo, hace que los ejemplos sean muy extensos y se pierda el hilo del patrón general.
A pesar de lo anterior el libro es bastante explicativo, como para tenerlo de referencia.