<div>I'm a "she" not a "he". :-) But actually I don't believe I was a member of this group when I was working with the book "A Byte Of Python" I don't believe I ever described a problem with raw_input here. That concept seems pretty clear to me but as you say the OP hasn't described a specific problem. As I said before, it was the fact that the author was describing features that I was not seeing in the shell that prompted me to try to figure out the "new window" feature. As soon as I solved the shell problem I had no further difficulties understanding the concepts in the book. I just thought I'd share what worked for me. :-)</div> <div> </div> <div>The OP has not specified what his problems specifically are, but<BR> "earlylight <BR>publishing" described his problem before, and he was not understanding<BR> why <BR>the >>> prompt was expecting immediate keyboard input when he typed in
<BR>raw_input(). So a noob cannot figure out why it is advantageous to have<BR> a <BR>raw_input function that immediately asks for input. He thinks, "why<BR> can't I <BR>put the input in directly?" That is why putting a program into an edit <BR>window is very advantageous.<BR><BR>I believe it is very likely that raw_input() is the culprit of<BR> confusion <BR>here. <BR></div><p> 
<hr size=1>Never miss a thing. <a href="http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs"> Make Yahoo your homepage.</a>