I'm recently at the beginning of chapter 11 now. It took me about 3 weeks long to read.
The first time I'm reading the first chapter of this book, I felt perplexed by it's overwhelming amount of code. Then, I peeked at the end of the book to realized that it has 1556 pages long. As I read the book page by page, I felt a bit uncertain and decided to skip to chapter 2. Chapter 2 mainly talks about os and sys module in python, the modules that form the core of much of Python's system. I learned a lot from here, and get exited by the detailed explanation.
In chapter 3, I just get known about pipe, command line, and standard streams in comprehensible way. I get a grasp regarding sys.argv, sys.stdout, sys.stdin, etc. Every substance has it own code example to get more precise understanding.
Same concept apply on Chapter 4 and 5 with different topic obviously. But in chapter 6, I concluded that some of the examples isn't interesting. I just picked 3 projects (web-redirect, file-size-detector, and file-split-join), which I think is catch my attention.
As I began my journey in chapter 7, I get a clear description about how .pack() function is work and it helped my widget placement constrain in tkinter. In the next two chapter, it just introduce the basic widgets usage, but its worth reading.
And here began the chapter 10, I learned more about how to code GUI in different ways. The thread and streams method are interesting to read.
My conclusion is, this book isn't that bad. It may a bit verbose (even I think the same). But it give you more detailed explanation about some particular subjects. This book chapters are connected with one another. You will find it hard to skip one chapter to be able to follow along the book, but the author has code repository stored in his website. The author is know what he's doing, it's okay if this book bored you by its long page bible, you can leave it anyway.
Overall this is a good book, well written and structured. It's answer what, how and why question (you may have a hard time figured out how the code is working, thought). This book implicitly will teach you how to write readable code, which is an important skill for programmers to learn. If you have a spirit to complete this book, you must be persist and patient. You will get bored or unmotivated in the middle of road (I felt that too), but the tread off is fundamental knowledge about specific subjects (assuming that the other people may not read all the chapters).