"Luke Paireepinart" <[EMAIL PROTECTED]> wrote
> And what's all of this 'command-line' business? Your python script
> is
> the same when run by double-clicking as it is when run from idle:
I'll have to disdagree with you here Luke.
IDLE changes script behaviour in quite a number of subtle
ways
"Alan Gilfoy" <[EMAIL PROTECTED]> wrote
> The command line program seems to work through my program OK, but
> the
> command line program shuts down immediately after the program has
> run
Yes this is normal behaviour.
There are several ways around it, one of which is the
raw_input trick you ha
Bob has answered your original question, but I'd like to make some
observations.
Alan Gilfoy wrote:
> Hello All.
> I've been concocting some simple programs based on an online tutorial,
> and I, of course, save a program as a .py file.
>
> When running my program via IDLE, once I've cleaned out
Alan Gilfoy wrote:
> Hello All.
> I've been concocting some simple programs based on an online tutorial,
> and I, of course, save a program as a .py file.
>
> When running my program via IDLE, once I've cleaned out the bugs, it
> works as I expect it to.
>
> But I noticed something else:
>
> Cl
