Having a book is like having an additional monitor full of information that is uncompromising on your task. It's also wonderful to read, and easy to pop open even when your laptop isn't out, and you're just curious "I wonder if Array has a method to do ...."
A final note, because of that, having a paper reference (especially an annotated one) lends itself strongly to actually reading large swaths of it, instead of just finding the method you need and putting it away. With it being clunky, you don't want to do a lookup twice, so you open it and keep it open, and often read through a module/class' entire method list. That really improves your knowledge.
So in short, because it encourages good work and work practices.
This is probably pretty intentional. I had Dave as a professor for several C based classes and he recommended K&R highly. In the introductory course, he even used it as the textbook.
(btw I also have attended one of his new Chicago Python classes - recommended, he's a great teacher)
The closest thing to K&R C for python is Python Essential Reference by Beazley. The structure mirrors K&C. The first chapter is a "tutorial introduction", basically a quick survey of the language, followed by about 150 page explaining the language. It is dense and terse and to the point. The remaining 400 pages are a reference for the python library.