Disclaimer: following a post on Google+ by a Packt representative, I volunteered to do a review of IPython Notebook Essentials and got a free copy as an ebook (I used the pdf format).
The verdict: Not recommended in its current state.
IPython Notebook Essentials starts very well. It suggests to use the Anaconda 3.4 distribution (which I have on my computer - more on that later) or connecting online using Wakari. Both methods worked fine for simple examples.
In chapter 1, we are given a quick tour of what the IPython notebook can do using the modeling of a cup of coffee as an example. The idea, on its own works well. [As a scientist, I found the use of degree Farenheit a bit odd and reminded me of books I read that were written 50 or more years ago.] However, while the authors used variables that follow the normal Python convention, separating names by underscore as in
temp_cream, the code formatting is at times atrocious as variable names are sometimes split up after an underscore character as in the following two lines of code:
initial_temp_mix_at_shop = temp_mixture(temp_coffee, vol_coffee, temp_
cream, vol_cream)
which are, ironically enough, in bold in the text as the author wants us to focus our attention on their meaning (but no mention of the error in formatting).
While I usually prefer holding a paper book over reading an ebook on my screen, I must admit that being able to copy-paste code samples beats having to retype everything. So, it was possible to quickly reproduce the examples by copy-pasting and fixing the typos to run the examples.
However, a much better way exists which is often used by Packt books: making code samples available for download. The IPython notebooks have been designed for easy sharing. Here, the author has chosen not to make use of this. This, in my opinion, is something that is a major flaw in this case.
Chapter 2 covers in more details the notebook interface. This is undoubtably the most important chapter of the book for anyone who wishes to learn about the IPython notebook. It covers a lot of grounds.
However, I encountered many problems, some more serious than others. The first, which is perhaps more an annoyance than a real problem, is that one example intended to show code completion using the tab key is given as follows:
print am
Python programmers will immediately recognize this as being a Python 2 example. However, as far as I could tell (using ctrl-f "python 2") there isn't a single mention anywhere that Python 2 is used.
I happened to have the Anaconda 3.4 distribution installed (as recommended) but with Python 3.4 and not Python 2. Python 3 is now 6 years old and there is no excuse to focus on an old, and soon to be obsolete, version of Python without at least mentioning why that choice was made. Minor syntax difference, like adding parentheses for print statements, are easily fixed; some more subtle ones are not. Furthermore, while I had the Anaconda distribution installed, I was still using the online Wakari site to work through the examples, so that was not a major problem at that point.
While still in chapter 2, we are invited to replace "%pylab inline" by "%pylab" and run an example again to see a plot appear in a window (I first assumed a separate browser window) instead of being shown in the document. This does not work using the online Wakari site: the window is actually a Qt window, not something that works in a browser. So, to try this example, I had to start my local version and recopy the code, which worked correctly.
Shortly thereafter, we are introduced to more "magic" methods and invited to try running a cython example, loading from a local file. This did not work. The recommended "%%cython" magic method is no longer working in the latest IPython version included with the Python 3.4 Anaconda 3.4 distribution. After a while, I found the proper way to run cython code with the latest version BUT the example provided raised a (numpy-related?) syntax error. I copy-pasted the code from my browser to the Wakari online version and it worked correctly, confirming that I had not made an error in reproducing the code given by the author. However, I was not able to figure out the source of the error using the local version.
After finishing Chapter 2, I stopped trying to run every single examples and simply skimmed the book.
Chapter 3 focuses on producing plots with matplotlib, including animations. While not specific to the IPython notebook, this topic felt like an appropriate one to cover.
In Chapter 4, we learn about the pandas library which has very little to do with the IPython notebook. The situation is similar with Chapter 5 which covers SciPy, Numba and NumbaPro, again three libraries that have very little to do with the notebook as such. The choice of NumbaPro struck me as a bit odd since it is a commercial product. True enough, it can be tried for free - however, it is not something that I would consider to be an "essential" for the IPython notebook.
I know very little more about the IPython notebook than what I have learned from this book. However, I do know that it is possible to write extensions for the IPython notebook which is something that I would have thought should be included in any book titled "IPython Notebook Essentials", well before discussing specialized libraries such as Pandas, SciPy, Numba and NumbaPro.
There might very well be other topics more notebook specific that should be included, but I have no way to know from this book.
The book includes three appendices: a brief IPython notebook reference card, a brief review of Python, and an appendix on Numpy arrays. Both the Reference card and the Numpy arrays appendices seem like worthwhile additions. However, the brief review of Python seems a bit out of place. By including code like:
def make_lorenz(sigma, r, b):
def func(statevec, t):
x, y, z = statevec
return [ sigma * (y - x),
r * x - y - x * z,
x * y - b * z ]
return func
in Chapter 2, the author seems to assume, and rightly so in my opinion, that the reader will be familiar with Python. However, the appendix only covers the standard Python construct that one may find in a beginner's book intended for programmers that are familiar with other languages. As such, the Python review appendix seems just like a filler, increasing the page count while adding nothing of value to the book. Thankfully, it is relegated to an appendix instead of being inserted in an early chapter.
In summary, about half of the book contains information of value for someone who wants to learn about the IPython notebook itself; the choice of Python 2 over Python 3 is odd, and almost inexcusable given that it is not even mentioned anywhere; the lack of downloable code samples" (mostly IPython notebooks in this case) greatly reduces the value of this book and is something that could be remedied by the author. In fact, given the typos mentioned (where variable names are split over two lines), downloadable copies of notebooks
should be made available.
As I write this review, Packt is having a sale during which ebooks are available for $5. At that price, I would say that IPython Notebook Essentials is worth it if one wants to learn about the IPython Notebook; however, based on a quick scan of other Packt books covering the IPython notebook, I believe that better choices exist from the same editor.