At 09:23 AM 10/4/2006 +0100, Paul Moore wrote: >On 10/4/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: >>At 11:12 PM 10/3/2006 +0100, Paul Moore wrote: >> >Also, the automatic pause would annoy me. How would you make it *not* >> >happen if I ran the command from a console window I already had open? >> >>The idea would be to register a separate "easy_install-win.exe" under >>"easy_install" in App Paths. This version would pause after termination, >>while the normal version would not. Since console programs invoked via the >>App Paths mechanism *always* get their own new window, this should work out >>nicely. > >Sadly, not true. The replacement console program 4NT (which I use >pretty much exclusively) uses App Paths to locate executables. So if >you (in effect) alias easy_install to easy_install-win, you'll break >it for 4NT users.
Ah crap. I wonder if there's any way to tell whether you're the only process on a particular console? That would fix this, I guess. There's a GetConsoleProcessList() API, but it doesn't even work on Win2K as far as I can tell; a minimum of XP is required. :( Further Googling shows that many other people with more Windows savvy than me have tried going this path and failed -- apparently the only way to find out who your parent process is is an undocumented function in ntdll. :( >Why not just have the second executable with a simple to type name >(easy_installw, say) and suggest people type *that* in the Run window? >Keep it simple! That doesn't solve the problem for other Python console scripts; It'd be ideal if I could solve this in the .exe launcher itself. _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
