- Taschenbuch: 404 Seiten
- Verlag: Packt Publishing (26. Juli 2010)
- Sprache: Englisch
- ISBN-10: 1849511268
- ISBN-13: 978-1849511261
- Größe und/oder Gewicht: 19 x 2,3 x 23,5 cm
- Durchschnittliche Kundenbewertung: Schreiben Sie die erste Bewertung
- Amazon Bestseller-Rang: Nr. 250.153 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
Python 3 Object Oriented Programming (Englisch) Taschenbuch – 26. Juli 2010
|Neu ab||Gebraucht ab|
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Über den Autor und weitere Mitwirkende
Dusty Phillips is a Canadian freelance software developer, teacher, martial artist, and open source aficionado. He is closely affiliated with the Arch Linux community and other open source projects. He maintains the Arch Linux storefronts and has compiled the Arch Linux Handbook. Dusty holds a master's degree in computer science, with specialization in Human Computer Interaction. He currently has six different Python interpreters installed on his computer.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
First, there is a nice little intro chapter that should be called 'just enough UML'. The author gives you a most sensible fly by that is useful for those who aren't partial to having to generate CYA documentation in large companies. Use case fundamentals are related to UML class diagrams and then into sequence diagrams (exactly how I've always done things). If you have always thought Rational Rose was a bit of an overkill, but you like taking a marker to an art pad or a white board instead for designing software, you'll like this.
Second, you are treated to a brisk walk through of Python, and the author is quick to point out how it differs from other OO environments, gives a nice explanation of the parts where Python philosophy might contradict what you've been taught with the other languages and quickly introduces you to the niceties of Python that you aren't accustomed to.
Finally, I found this book answered questions that others didn't. You'll see that the author is almost reading your mind in some places (that is, if again, you've been doing OO for a while with other languages). If you are into design patterns, so much the better.
I found this book to be a quick study, without muddying up the water with extraneous detail that isn't necessary. I would not likely recommend this book to someone who is just getting started with software development for the first time ever, but if you are a somewhat experienced hacker who understands OO and values the importance of mixing in just enough design with your coding (before, during and after that is), this book may definitely be for you.
I am just under half-way through the book and I must say that so far this is the best resource that I've found to teach object-oriented python programming. The author explains absolute imports vs relative imports as well as discussing the necessary folder/file structure required of OOP projects.
I would recommend this book to those wanting to learn the theory of OOP. The author does a good job of explaining the OOP theory and how it differs from other programming paradigms (aggregation, composition) as well as when to (and not to) use OOP.
Although this book is meant for Python 3.X I've been using 2.7.X because that's what is installed at my work. There are a few nuances between the "Classic classes" & "New classes". I won't go into the differences here but that just knowing that there is a difference between the two should put the reader on the right track to solving any issues that arise.
Feel free to comment on this review with questions regarding the differences between the New & Old Style Python classes.
My only critique is that the book had several typos, and one of the source listings was obviously missing a few lines. It seemed to be more of a problem with this book than the average technical book and was annoying, especially the source code listing. I stared at that code for 15 minutes before I found the problem.
All in all, the book was fun to read and educational. If you are ready to move beyond mere scripting in Python, do yourself a favor and pick up a copy of this book. Please don't attempt anything like an Abstract Factory Design Pattern in Python before you know how to do it the Pythonic way, as shown in this excellent book.