Gavin Bauer wrote:
My DOS window (running in windows ME) closes the second it finishes
running my programs. As you can imagine, this makes it hard to see the
results. I've gotten in the habit of putting raw_input(Press enter to
exit) at the end of every program, and in addition to being pain in
My DOS window (running in windows ME) closes the second it finishes
running my programs. As you can imagine, this makes it hard to see the
results. I've gotten in the habit of putting raw_input(Press enter to
exit) at the end of every program, and in addition to being pain in
the butt, it often
Gavin Bauer wrote:
My DOS window (running in windows ME) closes the second it finishes
running my programs. As you can imagine, this makes it hard to see the
results. I've gotten in the habit of putting raw_input(Press enter to
exit) at the end of every program, and in addition to being pain
When I have a Python script generating a lot of output, I either open
an output file and then print to it with
fp = open(results.txt,w)
printfp,stuff
or I redirect output to a file from the command line using (also
works on Unix), for example
python foo.py results.txt
An alternative is to
I tend to run cmd and cd to the directory of the script, then run
it. This way, the window doesn't close, and I can read any errors that
occur without interruption. Optionally, you can run cmd and simply
drag the script you want to run into the window. That pastes its path
(in quotes) into the
Gavin Bauer [EMAIL PROTECTED] writes:
Thank you, and please make all answers simple enough to be understood
by a highschool student and his father :) .
You might like to try IDLE, which is included with Python.
--
http://mail.python.org/mailman/listinfo/python-list
Gavin Bauer said unto the world upon 2005-01-07 15:47:
My DOS window (running in windows ME) closes the second it finishes
running my programs. As you can imagine, this makes it hard to see the
SNIP
Thank you, and please make all answers simple enough to be understood
by a highschool student and
