Python Essential Reference (4th Edition) 4th Edition

I almost passed on this book because of its 2009 publication date, but I am really glad I did not. The book was released at a critical time in Python history when Python 3 was just released. The author makes clear what the main distinctions between the two versions are.

The first 200 pages deal with the basic languages features and this part of the book was highly readable with well explained details. Examples given are practical. When introducing generators and co-routines the code was simple and easy to understand.

From page 200 on the reference section of the book starts. I found these parts to be slightly less readable although coverage was extremely thorough. For many of the standard libraries, the entire list of functions and parameters are listed. The code here focused on operating system calls, networking, socket, concurrency, and lower level web programming details. It is generally geared towards a system's programmer rather than an OOP programming.

My main complaint about the book is the size of text which is maybe 8 point font. The text should have been at least 2 font sizes bigger as I had to read quite close to the book.

Overall this is an excellent reference for Python and great to have by your side when programming.

I'm sick and tired of hearing people recommend to beginners that they read "Learn Python The Hard Way"! That book is absolutely terrible! This book is much better. Yes, it's a desk reference but this book starts out with a quick tutorial (one chapter) that covers the basics. It's a fast tutorial and a complete desk reference all in one. The author isn't an ESL student (he can construct a proper English sentence), the book is very accurate and contains very few typos. What else could you ask for?

Python Essential Reference (4th Edition) is a nice reference guide.

the table of contents is well organized into 2 groups actually, which is helpful when looking for a concept rather than a specific syntax issue.

unfortunately, the book uses python2 as the foundation (It still references py3 but often as a throw away--example: 2 paragraphs of explanation and a side now that it's done a different way in py3), so in that respect, it is a little outdated.

If you use Python3 (which, at this point, you likely do), wait for the 5th edition.

David Beazley's "Python Essential Reference, Fourth Edition" covers Python 2.6 and 3.0, and is thus quite (though not completely) up to date. The author has in essence chosen to present the intersection of the two branches, i.e. omit features of Python 2 that have been removed from Python 3. This volume's pace is rapid and the coverage is quite extensive, so this probably shouldn't be the first Python book one reads.

The Good: this book is approximately 700 pages long; even so, it's not that bulky and is therefore quite manageable. It is split into two parts: 200 pages on the language and roughly 400 pages on the library. The first part is very good, while the second part is unrivaled as of this writing (though this may change when Doug Hellmann's "The Python Standard Library by Example" comes out). Thus, the reader essentially gets two books for the price of one: the part on the language can be read linearly, while the library part can be read in chunks as the need arises. The book also includes an extremely useful Index which is approximately 80 pages long (and also contains unexpected entries, e.g. "chicken, multithreaded, 414"). Moving on to the material covered: Beazley includes an appendix on Python 3-specific concepts, but also offers useful advice on Python 3 throughout the main text (e.g. "To keep your brain from exploding, encoded byte strings and unencoded strings should never be mixed together in expressions"). I particularly enjoyed the sections on decorators, generators, and coroutines in the chapter on functional programming. Beazley has also posted on his website two tutorials on these topics that nicely complement the material in the book. Similarly, the chapter on multiprocessing and threading is impressive, and forms a nice set with the author's talk slides on the Global Interpreter Lock -- it's important to note that Beazley used to be a professor of Computer Science. Probably the most significant aspect of this book is the abundance of examples. I'm pretty sure the phrase that is most often repeated in this volume is "Here's an example". The examples are always enlightening, sometimes clever, but never obfuscating. Finally, the writing may not be flawless but overall it is quite good. Of course, any reference text is bound to be somewhat dry, but within the confines of the genre Beazley has truly done wonders: he has a personality and he's not afraid to show it. This jovial aspect of the writing is present when giving advice (e.g "Try not to mix threads and multiprocessing together in the same program unless you're vastly trying to improve your job security", p. 435), or just for its own sake (e.g. "If you change the code to only poll after every six-pack of beer", p. 469)

The Bad: chapter 1 is fun to read but it is deceptively titled ("A Tutorial Introduction"). For example, Beazley uses a decorator and the seek file method, without explaining anything about either of them. Of course, this book isn't supposed to be introductory, so strictly speaking my quibble is with the first chapter's title, not its content. The biggest problem I encountered while reading the book was the page layout in the majority of Part II: a module is introduced and then its methods are described by showing a name in bold, followed by a description on a separate line. This confused me to no end: whenever I saw a name, for a split second I would wonder if I should look up or down to find the description. This could have been avoided if the more standard tabular form had been chosen more often: name on one column, description on the other. Of course, I understand that this would have increased the size of the book considerably, perhaps prohibitively so. Moving on to more detailed complaints: for some modules (e.g. struct, shutil, os.path) Beazley gives a listing of the contents but, unfortunately, no corresponding examples. To be fair, he does use os.path functionality in a number of places throughout the book (though the index is no help tracking them down), just not in the appropriate section. Delving into even more detail: any book of this breadth is bound to contain minor errors. Here's a selection of such slips, all drawn from the same chapter: in some cases the prose is obscure, e.g. "A method is a function that performs some sort of operation on an object when the method is invoked as a function." (p. 33); sometimes a statement is contradicted in a later chapter, e.g. we read on p. 39 that "Sequences represent ordered sets of objects indexed by non-negative integers and include strings, lists, and tuples." only to find out on p. 68 that "Negative indices can be used to fetch characters from the end of a sequence."; similarly, on p. 45 we read that for dictionary methods like keys() "in Python 3 the result is an iterator that iterates over the current contents of the mapping", while on p. 632 we learn that "these methods return so-called view objects".

These days, the aspiring intermediate Python programmer doesn't have too many books to choose from: Martelli/Ravenscroft/Ascher's "Python Cookbook" is out of date, Ziade's "Expert Python Programming" contains too much material that is not Python-specific, and Alchin's "Pro Python" is only ~ 250 pages long. Thus, for the time being Beazley's "Python Essential Reference" is the obvious choice for a second book on Python. All in all, four and a half stars.

Alex Gezerlis

Read this book after you have a bit of knowledge about Python and you will be well-rewarded. I'm only 100 pages into it so far, but I really like it. This is my 2nd book on Python, the first ("Introducing Python:...", by Lubanovic) was a faster read but left many open questions. The prices of the books were about the same. You'll definitely get your money's worth on this volume! Obviously, some experience with programming languages (such as the matter of "constructors" and "inheritance", for instance) is expected.

Update (after reading 200+ pages) It is easy for me to agree with all of the reviewers who praise this book, and I can understand the point of view of some of those who are critical. In some cases, additional examples would be helpful, and perhaps even necessary. However, with any effort at all, you will surely be able to locate some online. But.., consider again the title of my review.