Daniel Stutzbach wrote: > Hmmm. So maybe what's needed is a *third* kind of exe that > gets launched when you double-click a .py file, that keeps > its console open after the script finishes? > > Picture command-line usage of python. You're sitting at your prompt, > and you run a python script. It pops up a *new* window and you have to > interact with that.
That's why I just suggested a *third* exe. It wouldn't be used as the command line interpreter -- it would only get launched by double-clicking a .py file in the gui. The current behaviour of having the gui launch the normal command line interpreter for .py files is almost useless, because the window disappears before you can see the output. -- Greg _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com