On 11/22/2011 10:43 PM, Dennis Lee Bieber wrote:
On Tue, 22 Nov 2011 19:46:01 -0800, "W. eWatson"
<wolftra...@invalid.com> declaimed the following in
gmane.comp.python.general:
Of course, Dennis'
C:\Python26\Lib\site-packages\pythonwin\Pythonwin.exe
wouldn't work either.
If you didn't install an ActiveState packaged version, nor hand
installed the win32 extension package into a Python.org installed
system, you won't have PythonWin.
I did a Win 7 search Pythonwin.exe, and found nothing. However,
sometimes that search fails even when though there is something on the
PC that matches the search.
There is a pythonw.exe under C:\Python32.
And has been mentioned at least three times in the last week --
pythonw.exe is the version of the Python interpreter that is supposed to
be the default application for .pyw files. It is the version that does
NOT open a console window for stdin/stdout (IOWs, it is meant for use by
Python scripts that use a graphical library for all I/O -- Tk, wxPython,
etc.). If you ran a graphical script using the plain python.exe it would
open a console window that would just sit there until the script exited.
Glad to hear you're keeping count. :-) I'll pin it on my wall. Don't use
graphics.
--
http://mail.python.org/mailman/listinfo/python-list
