2008/7/4 "Martin v. Löwis" <[EMAIL PROTECTED]>:
> and find installers annoying that ask too many questions
So do I, but not as annoying as installers that do the Wrong Thing
because they didn't ask! ;-)
Still, it's your call.
> In any case, try installing with
>
> msiexec /i 'ProgramMenuFolder=C
On Fri, 04 Jul 2008 16:19:34 +0100, Tim Rowe wrote:
> pythonw.exe (that's the windows executable, right?)
python.exe and pythonw.exe are both Windows executables. There are no non-
Windows executables in a Python for Windows package.
python.exe is used for console apps or interactive sessions.
> Is it worth flagging as an issue somewhere the fact that the pywin
> installer assumes a particular structure for the start menu
No. This is the first time in several years that this was reported,
and chances that this gets fixed in the upcoming years are very low,
unless a patch gets contribute
2008/7/4 Tim Golden <[EMAIL PROTECTED]>:
> Ummm. That's the Python interpreter but without a window so
> (unhelpfully, from your point of view) it's doing exactly the
> right thing.
>
> I assume you were trying to run the PythonWin Python
> interpreter and dev env? On my system, that's:
>
> C:\Pyt
Tim Rowe wrote:
I have Python 2.5 working just fine on my system.
I've tried downloading and installing the MS Windows Python
extensions, but can't get pythonw.exe (that's the windows executable,
right?) to do anything. I double-click it, nothing happens. I run it
from a command prompt, it just
I have Python 2.5 working just fine on my system.
I've tried downloading and installing the MS Windows Python
extensions, but can't get pythonw.exe (that's the windows executable,
right?) to do anything. I double-click it, nothing happens. I run it
from a command prompt, it just returns me to the
