could be reduced by 50% if the author had left out many personal

opinions and issues. My job is to learn Python, not to read countless

comments on the Colorado winters. He keeps mentioning that

well "be getting to <some topic> later", but that later

never quite materializes. In the very first intro chapter

he shows the reader an example of a fairly complicated

python program (includes various classes, etc), but when

you type the thing in, and run it, it fails because you

haven't built the classes that it depends upon. Why did he

take up 2-3 pages demonstrating this type of program at this

early hour? He didn't get into discussing the very basics

of the language until half-way through the book (Strings, slices,

Dictionaries, lists). I learned about these in the first

half-hour reading Guido's (free) tutorial (in html format).

I felt cheated that he can charge $45.00 for this long-winded

nothing of a book. My advice: keep the $45.00, and read

Guido's Tutorial.

==pete==