ACCU Home page ACCU Conference Page
Search Contact us ACCU at Flickr ACCU at GitHib ACCU at Google+ ACCU at Facebook ACCU at Linked-in ACCU at Twitter Skip Navigation

Search in Book Reviews

The ACCU passes on review copies of computer books to its members for them to review. The result is a large, high quality collection of book reviews by programmers, for programmers. Currently there are 1918 reviews in the database and more every month.
Search is a simple string search in either book title or book author. The full text search is a search of the text of the review.
    View all alphabetically
Title:
Python Developers Handbook
Author:
Andre Lessa
ISBN:
0 672 31994 2
Publisher:
Sams
Pages:
930pp
Price:
£32-99
Reviewer:
Francis Glassborow
Subject:
python
Appeared in:
13-2
The same caveats apply to my review of this books as apply to my review of Core Python Programming, mainly I have to take the technical correctness as a given.

First of all this author is concerned at trying to sell me on the value of using Python. He takes a good deal of space up front telling the reader why Python is better than other languages. I must admit that this kind of thing causes my hackles to rise. What would I be doing reading this book if I did not think Python had something to offer? Why insult my intelligence with a blatant 'sales pitch'? Just tell me what Python is and how to write it and let me be a judge of its relative merits. Of course a neutral statement that Python does this differently than X is fine. For example, as a C++ programmer it would help me to know that identifiers in Python are untyped references to data (i.e. the identifier takes on the type of whatever it currently refers to). I need things like that said clearly up front so that I am not deceived by what I see. What I do not need is to be told that this is a better way to use identifiers than the C++, Java or Smalltalk way. Different is fine, that is an objective statement, better is not, that is subjective and often depends on the surrounding context.

I have do doubt that there is plenty of good material in this book, but the author lacks a clear view of who he is writing for and just throws in everything but the kitchen sink. For example, why is he taking space to tell me how to compile Python (and he means the environment and interpreter, not Python source code)? If I am a Python Developer, I should already have a working version, and if not I will have to collect one from elsewhere (and the web sites have fully compiled versions available for all common platforms).

I think a book that was half the size, written with a greater degree of discrimination would be far better value for money, even at the same price. While this is not a bad book, more focus and a firmer control over the content is needed for this to become a good book.