Re: [Python-3000] Windows gui vs. console

2008-02-15 Thread Phillip J. Eby
At 02:18 PM 2/15/2008 +0200, Niki Spahiev wrote: >Phillip J. Eby wrote: > > That's actually a separate problem from the one Paul and I are > > talking about, one that I'm not even going to *try* to solve. (Being > > as I already have, and failed miserably.) Hell, I'm not sure Windows > > even has

Re: [Python-3000] Windows gui vs. console

2008-02-15 Thread Niki Spahiev
Phillip J. Eby wrote: > That's actually a separate problem from the one Paul and I are > talking about, one that I'm not even going to *try* to solve. (Being > as I already have, and failed miserably.) Hell, I'm not sure Windows > even has a way to *tell* whether your app was launched from the

Re: [Python-3000] Windows gui vs. console

2008-02-09 Thread Suraj Barkale
Greg Ewing canterbury.ac.nz> writes: > > Paul Moore wrote: > > On Windows, GUI vs Console is a property of the EXE file, > > and the differing behaviour is built into the OS loader. > > Would it be feasible for it to always start up as a gui > app, and then create its own console window (a fake

Re: [Python-3000] Windows gui vs. console

2008-02-08 Thread Nick Coghlan
Greg Ewing wrote: > 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 prom

Re: [Python-3000] Windows gui vs. console

2008-02-08 Thread Greg Ewing
Phillip J. Eby wrote: > Hell, I'm not sure Windows even > has a way to *tell* whether your app was launched from the command line > or otherwise. It wouldn't have to, if the .py extension were bound to a different executable from the standard command line interpreter, in the same way that .pyw i

Re: [Python-3000] Windows gui vs. console

2008-02-08 Thread Greg Ewing
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 pyt

Re: [Python-3000] Windows gui vs. console

2008-02-08 Thread Christian Heimes
Facundo Batista wrote: > When the process is issued as a Service, it don't even HAS > stdin/stdout (not that is redirected to NUL). It don't even exist. GUI apps don't have standard streams stdin, stdout and stderr, too. The variables are defined when the code is compiled but during runtime the st

Re: [Python-3000] Windows gui vs. console

2008-02-08 Thread Facundo Batista
2008/2/8, Daniel Stutzbach <[EMAIL PROTECTED]>: > 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. Not a great user experience. Also, piping data to or from the > script is imposs

Re: [Python-3000] Windows gui vs. console

2008-02-07 Thread Phillip J. Eby
At 03:59 PM 2/8/2008 +1300, Greg Ewing wrote: >Paul Moore wrote: > > As Phillip says. Windows console and GUI executables are completely > > different in behaviour. Don't try to fight it. You need two distinct > > EXEs. > >Hmmm. So maybe what's needed is a *third* kind of exe that >gets launched wh

Re: [Python-3000] Windows gui vs. console

2008-02-07 Thread Daniel Stutzbach
On Feb 7, 2008 8:59 PM, Greg Ewing <[EMAIL PROTECTED]> wrote: > Paul Moore wrote: > > As Phillip says. Windows console and GUI executables are completely > > different in behaviour. Don't try to fight it. You need two distinct > > EXEs. > > Hmmm. So maybe what's needed is a *third* kind of exe tha

Re: [Python-3000] Windows gui vs. console

2008-02-07 Thread Greg Ewing
Paul Moore wrote: > As Phillip says. Windows console and GUI executables are completely > different in behaviour. Don't try to fight it. You need two distinct > EXEs. 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 o

Re: [Python-3000] Windows gui vs. console

2008-02-07 Thread Paul Moore
On 07/02/2008, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > At 09:52 AM 2/8/2008 +1300, Greg Ewing wrote: > >Would it be feasible for it to always start up as a gui > >app, and then create its own console window (a fake one > >if necessary) if it decides it needs one? > > No, because that would make

Re: [Python-3000] Windows gui vs. console

2008-02-07 Thread Phillip J. Eby
At 09:52 AM 2/8/2008 +1300, Greg Ewing wrote: >Would it be feasible for it to always start up as a gui >app, and then create its own console window (a fake one >if necessary) if it decides it needs one? No, because that would make it impossible to write a sane command-line app. Imagine if runnin

[Python-3000] Windows gui vs. console

2008-02-07 Thread Greg Ewing
Paul Moore wrote: > On Windows, GUI vs Console is a property of the EXE file, > and the differing behaviour is built into the OS loader. Would it be feasible for it to always start up as a gui app, and then create its own console window (a fake one if necessary) if it decides it needs one? Doing