pythonwin broke

[Jive]

I've un-installed Python 2.4, re-installed Python 2.3 and PythonWin for 2.3,
but it's still broke.

When I start PythonWin, sometimes it looks like it is going to be okay. But
as soon as I open a .py file, the interactive window grabs the focus and
will not let go. I am stumped.

Is there something PythonWin uses that I could try re-installing? WxPython
maybe?

 

[Steve Holden]

I've un-installed Python 2.4, re-installed Python 2.3 and PythonWin for 2.3,
but it's still broke.

When I start PythonWin, sometimes it looks like it is going to be okay. But
as soon as I open a .py file, the interactive window grabs the focus and
will not let go. I am stumped.

Is there something PythonWin uses that I could try re-installing? WxPython
maybe?

This isn't something I can ever remember happening. You might consider
asking on the python-win32 list, which is more specifically directed at
Mark Hammond's stuff.

regards
Steve

 

[Jean Brouwers]

We just went through a similar install-uninstall-reinstall cycle with
Python 2.4 and 2.3 on Windows XP SP2. Just uninstalling 2.4 and
reinstalling 2.3 was not sufficient.

It took several attempts to get things back to the original 2.3
configuration. After unininstalling both, we deleted all Python
related entries in the Registry and in the StartUp folder. Only after
that did the reinstalled 2.3 plus extensions work fine again.

/Jean Brouwers

PS) We backed out of using Python 2.4 since two of the extensions we
need did not work with 2.4 on Windows XP.

PPS) It looks like Python 2.4 and Python 2.3 can not co-exist (in
different folders under Program Files) but we did not investigate that
any further.

 

[Trent Mick]

PPS) It looks like Python 2.4 and Python 2.3 can not co-exist (in
different folders under Program Files) but we did not investigate that
any further.

That's not true. I have every version of Python back to 2.0 installed
and all running fine on my system. Obviously you can only have one of
your Python installations first on your PATH (and hence the one that
gets run by simply typing "python"). Also, you can only have one of you
Python installations registered as the default handler for .py files
(and hence the one that gets run by simple double-clicking on a .py file
in explorer or running a Python script without the extension from the
command line).

It is also possible that there is some little installer bug or detail on
your environment that is causing the problem. You could try
ActivePython. I regularly install and uninstall ActivePython 2.3 and 2.4
installers and both installs are still working fine.

Cheers,
Trent

 

[David Bolen]

It is also possible that there is some little installer bug or detail
on your environment that is causing the problem. You could try
ActivePython. I regularly install and uninstall ActivePython 2.3 and
2.4 installers and both installs are still working fine.

Just as another data point, I have all of Python 1.5.2, 2.0.1, 2.1.3,
2.2.3, 2.3.4 and 2.4 installed side by side on my Windows box, as
installed by their standard installers, without any problems. And
that includes uninstall/reinstall cycles for patch releases of
versions older than the most recent (e.g., putting on 2.2.3 after a
2.3 variant was already installed). The only real restriction is as
you noted - only one can own the file associations (or be associated
with the COM support for pywin32).

In case it matters, I do install everything as administrator for all
users and this is under 2K (my NT box has everything but 2.4).

-- David

 

[Jive]

I uninstalled Python and Pythonwin. I verified that there was nothing left
in the registry or the startup folder. I reinstalled Python using
Python-2.3.4.exe and Pythonwin using win32all-163.exe.

It's still broke.

The shortcut in the startup folder says

Target: C:\Python23\Pythonwin.exe
Start in: C:\Python23\lib\site-packages

When I open Pythonwin that way, once I open a file from the File menu, the
menu buttons on the new window and on the main Pythonwin frame become
inoperable.

I can keep that from happening by changing the Target to
C:\Python23\lib\site-packages\pythonwin\start_pythonwin.pyw. (Just a wild
guess on my part.) But then there's a different problem. When I try to run
a module, I get the message,


Traceback (most recent call last):
File
"C:\PYTHON23\lib\site-packages\Pythonwin\pywin\framework\scriptutils.py",
line 307, in RunScript
debugger.run(codeObject, __main__.__dict__, start_stepping=0)
File "C:\PYTHON23\lib\site-packages\Pythonwin\pywin\debugger\__init__.py",
line 60, in run
_GetCurrentDebugger().run(cmd, globals,locals, start_stepping)
File "C:\PYTHON23\lib\site-packages\Pythonwin\pywin\debugger\__init__.py",
line 35, in _GetCurrentDebugger
_CheckNeedGUI()
File "C:\PYTHON23\lib\site-packages\Pythonwin\pywin\debugger\__init__.py",
line 21, in _CheckNeedGUI
pywin.framework.app.CreateDefaultGUI(dbgpyapp.DebuggerPythonApp)
File "C:\PYTHON23\lib\site-packages\Pythonwin\pywin\framework\app.py",
line 392, in CreateDefaultGUI
appClass().InitInstance()
File "C:\PYTHON23\lib\site-packages\Pythonwin\pywin\debugger\dbgpyapp.py",
line 33, in InitInstance
win32ui.LoadStdProfileSettings(numMRU)
win32ui: The profile settings have already been loaded.

 

[Jive]

. You might consider
asking on the python-win32 list, which is more specifically directed at
Mark Hammond's stuff.

Okay. How do I find the python-win32 list? It's not a newsgroup,
apparently.

 

[Jive]

We just went through a similar install-uninstall-reinstall cycle with
Python 2.4 and 2.3 on Windows XP SP2. Just uninstalling 2.4 and
reinstalling 2.3 was not sufficient.

It took several attempts to get things back to the original 2.3
configuration. After unininstalling both, we deleted all Python
related entries in the Registry and in the StartUp folder. Only after
that did the reinstalled 2.3 plus extensions work fine again.

I've done that, but without success. Which versions of 2.3 and Pythonwin
did you use?

Jive

 

[Jean Brouwers]

Well, we made several attempts to install Python 2.4 with a number of
extension packages on Windows XP and used the binaries from the Python
site, not ActivePython.

Previous to 2.4, we did have several versions of Python installed on
Windows XP without any problem. We installed 2.4 as usual in a
separate directory under Program Files. But there were several
problems getting the 2.4 exe and IDLE started, in addition to issues
with some extensions. Plus 2.3.4 could not be started any longer.

Uninstalling 2.4 did not quite work and *may* have broken the existing
2.3.4 installation. Uninstalling and reinstalling that failed also,
until we manually cleaned up the Registry and StartUp folder.

As I mentioned, we did not investigate the 2.4 problem any further
since getting 2.3.4 back up and running was more critical than 2.4 due
to other problems with the extensions on 2.4.

Once all extensions exist for 2.4 we will try again. And maybe, we
should use the ActivePython builds then ;-)

/Jean Brouwers

PS) We had no problem with Python 2.4 or any extensions on Lunix.
Everything works fine there and all our Python code runs unmodified on
both 2.3 and 2.4 with extensions, without any failure or glitch. The
difference *may* be that we rebuild the distribution on Linux but not
on Windows.

 

[Jive]

Do an experiment for me. Open Pythonwin from the start menu. Use the FILE
menu to open a .py file. Now try to close the window you just opened using
the X button in the upper right. Did it close? Try closing Pythonwin using
its X button.

 

[Jive]

I installed ActivePython2.3. It does the same thing.

I am wondering if I have a corrupted MS Windows DLL somewhere. If so, is
there any chance I can figure out which one it is?

Jive

 

[Peter Hansen]

Okay. How do I find the python-win32 list? It's not a newsgroup,
apparently.

What happened when you typed "python-win32 list" into Google?
Was it broken at the time? ;-)

http://mail.python.org/mailman/listinfo/python-win32

 

[Jean Brouwers]

I'm not sure what Pythonwin is. The Python start menu shows "Python
(command line)" and "IDLE (Python GUI)" plus docs, etc.

Your experiment with IDLE works just fine. Both windows closed on
clickin X. This is Windows XP SP2 with Python 2.3.4 from the
Python.org site.

/Jean Brouwers

 

[Jean Brouwers]

One more test, but after selecting "Modules Doc" from the start menu.

The small pydoc window shows up, "Python documentation server ..." etc.
Clicking the X button results in a "pythonw.exe Application Error" with
the message:

The instruction at "0x..." referenced memory at "0x0..014". The
memory could not be "read". Click on OK to terminate the program.

Same Window XP SP2 machine running Python 2.3.4 downloaded from the
Python website (with just one extension, wxPython 2.4.2.4).

/Jean Brouwers