are good you'll find ample material to browse published books as final resourceyou can choose from collection of professionally edited and published reference books for python bear in mind that books tend to lag behind the cutting edge of python changespartly because of the work involved in writingand partly because of the natural delays built into the publishing cycle usuallyby the time book comes outit' three or more months behind the current python state (trust me on that--my books have nasty habit of falling out of date in minor ways between the time write them and the time they hit the shelves!unlike standard manualsbooks are also generally not free stillfor manythe convenience and quality of professionally published text is worth the cost moreoverpython changes so slowly that books are usually still relevant years after they are publishedespecially if their authors post updates on the web see the preface for pointers to other python books common coding gotchas before the programming exercises for this part of the booklet' run through some of the most common mistakes beginners make when coding python statements and programs many of these are warnings 've thrown out earlier in this part of the bookcollected here for ease of reference you'll learn to avoid these pitfalls once you've gained bit of python coding experiencebut few words now might help you avoid falling into some of these traps initiallydon' forget the colons always remember to type at the end of compound statement headers--the first line of an ifwhileforetc you'll probably forget at first ( didand so have most of my roughly , python students over the years)but you can take some comfort from the fact that it will soon become an unconscious habit start in column be sure to start top-level (unnestedcode in column that includes unnested code typed into module filesas well as unnested code typed at the interactive prompt blank lines matter at the interactive prompt blank lines in compound statements are always irrelevant and ignored in module filesbut when you're typing code at the interactive promptthey end the statement in other wordsblank lines tell the interactive command line that you've finished compound statementif you want to continuedon' hit the enter key at the prompt (or in idleuntil you're really done this also means you can' paste multiline code at this promptit must run one full statement at time common coding gotchas