Python 3 Object-oriented Programming: Building robust and maintainable software with object oriented design patterns in Python, 2nd Edition 2nd Edition

I was at first uncertain whether investing in a Python OOP book resource would be worth the money given the vast quantity of free resources online. I'm glad I did! I have roughly one year of programming experience (less than that in Python) and this book is very digestible, even for beginners. The book is very straight forward and built around examples which helps in giving perspective to OOP concepts covered throughout the book. If you're new to Python I would definitely recommend this book once you're ready to tackle OOP. Definitely keep it around as a reference once you've finished going through it.

Python 3 Object-oriented Programming is an complete journey into the inner working and concepts the make up OOP in Python. For those seeking to go beyond just a basic understanding and to have a large guide with example of the concepts, this is a great book. Although beginners could opt to choose a cursory tutorial that skims over the basics, you really can't go wrong with a more complete understanding provided in Python 3 Object-oriented Programming.

I implemented almost all the author’s example on a Microsoft Visual Studio platform with minimum issues. Some of the examples need some modification for this platform, but nothing major. I found the book easy to read and understand. This is the best Python Object-Oriented book I have found todate.

There are a few issues with the code samples provided with the book that will hopefully be sorted out in the next edition, if there will be one. Although I find it a fantastic introduction to object oriented programming concepts in general (very easy to follow and provides well thought out examples along with good principles), I can't get over how the author seems so self-involved. There are constant references to his blue eyes and "penchant for writing" throughout the chapters; reading the page-long foreword will definitely give the reader an idea of this. I didn't want or purchase a personal ad for some blue-eyed guy and his love of writing (self-help programming literature at that!); I bought a book to introduce myself to OOP principles and methods.

I now have read half of the book. It is the first book makes me truly understand what object orientated programming really means.The book is really well written. No trivial things. All the key points are elaborated naturally and are making a lot of sense.

This is an extremely complicated book which is unnecessarily verbose. Even simple concepts are presented in a complicated way. For every section I had to go through internet and do a lot of search to understand explanations

I have the first edition of this book. It is a fine book. But I find those responsible for marketing this new edition unconscionable for the lack of info about what is new? Why should I should buy the 2nd edition. Is this simply a reprinting? Authors work hard and publishers lag.

I instantly liked the introduction which is short, informative and personal. For me this can already be half the battle for a buying decision. The table of contents delivered the other half by reminding me that the Gang of Four’s Design Patterns was sitting on my shelf untouched for long. (It has been written in 1994, how time flies!) Dusty’s book seemed to be a fit occasion for having a fresh look at design patterns and see whether Python makes any difference. Furthermore, as the author freely admits in the introduction he has added a chapter about unit testing and one about concurrency which are not directly related to OOP, but which have nevertheless attracted my interest in this book.About 20% of the book’s pages (after 50% on OOP with Python) are dedicated to design patterns (chapters 9-11). Chapter 9 elaborates on the iterator pattern while the following two chapters cover 6 design patterns each. That’s roughly half of the design patterns described in Gamma et al. but I’m fine with the selection made. Chapters 1 (on OOD), 12 (on unit testing) and 13 (Concurrency) frame the book’s core.When reading I have had already a pretty good grasp about OOP but I did not know Python. Having said this I cannot judge how comprehensible this book might be for readers without programming experience but it looks for me like a smooth intro into object-oriented programming. Yet the author states “This is a practical book, not a textbook.“. The author is likely hinting at the absence of exercises (though the book contains several short think-about sections which have been titled ‘exercises’). According to my conception, this book is a practical textbook indeed.Soon after starting reading I got convinced that this book works for me as a great introduction to Python. Whether you are interested in learning Python, refreshing design patterns or whether you are curious where “pythonic OOP thinking” differs, this book is expository in a readable and concise fashion. Clearly, it should not be your first programming book.I don’t hesitate to give this book 5 stars.