Python Object-Oriented Programming: Build robust and maintainable object-oriented Python applications and libraries, 4th Edition

Dear Packt,I have found an awesome content inside the book. But the quality of the binding I received from the publisher is unacceptable. Its not the first time, i encountered the issue.Pl don’t spoil the journey of reading awesome content just because of your poor quality of presentation.BR,Matthew

Per imparare a muoversi su oop in python, un libro intuitivoLo consiglio

Para quem não conhece POO em PYTHON, aprende ao ler/consultar o livro. Deveria ter mais exemplos!Como não gosto de ver filmes online, está a ser óptimo.

Disclaimer: I'm no expert in OOP, and I decided to purchase the book for self-improvement. I have mostly experience in functional programming from a C/C++ standpoint. This is only a partial review for the 4th edition, since I'm currently skimming from one chapter to the other, mostly for comparison with the previous editions (e.g. 2nd). As I'm writing, I have the 2nd and 4th edition. I don't know the authors.Good points about the 4th edition:1)introductory first 5 chapters are well crafted. Some Case studies have been removed (e.g. Notebook, Real Estate) and others have been added, which, in case you have both editions, can be interesting to compare / go through.2)Compared to the previous editions, some sections have been expanded / added, like an entirely new chapter on Abstract Base Classes & Operator Overloading3) some explanations are quite clearNegative points about the 4th edition:1) an updated GIT repo for the 4th edition would have been helpful (e.g. compare it with Aurelien Geron's Hands-on ML book). I can only find the 2nd and 3rd edition for Packt on Github.2) some sections (e.g. about do's and don'ts) are really verbose, and it would have helped to back up some statements with some code to understand what truly happens if something goes wrong.3) some examples don't seem to work out of the box.As I'm reading the Chapter on Common Design Patterns ( Ch11), in particular the section on decorating a socket, the try statement in dice_response() (page 466) returns a variable belonging to a dice object ( dice.dice_roller(request) ), while there are no hints about a Dice class in the entire paragraph about the Decorator Pattern. A Dice class is introduced in Chapter 11 only from page 488, in the Command Pattern.This section could have been written in a better way, in my opinion. After all, the section on Design Patterns (DP) is what makes OOP more interesting.Update: I was comparing the Decorator Pattern section with the implementation on the previous edition, and in this case, the code runs smoothly. For this reason, probably it would be better to read first the Design Pattern Section on the previous editions, and only afterwards to go through the 4th edition.I have to go through the remaining sections, but I'll consider backing up with some other references like :1) Luciano Ramahlo's Fluent Python (2nd edition)2) Practical Python Design Patterns, by Wessel Badenhorst3) Python Programming With Design Patterns, by James Cooper (from IBM, sharing same floor of John Vlissides from the Gang of Four)

Despite its unfortunate initialism, POOP is money well spent. If you already have some experience with python, this book will take you to a next level in Python programming, and teach you along the way some good practices, how to improve readability and some common useful design patterns. Thumbs up!