I have a specific PythonWin IDE problem -and a very general, but possibly misguided question:
1. When I start PythonWin, I get no interactive shell and when I try to do anything -PythonWin seems to go into some kind of loop, and grinds my machine to a halt. I have sometimes seen references re unable to save a file, when trying to execute a script -but rarely get that far. PythonWin has run fine on this (XP)machine -it just started doing this one day after a failed debug session. I have uninstalled both PythonWin and Python -and reinstalled to no avail. I get the problem with both 208 and 203 -and against Python 2.4.2 and 2.4.3. Given the fact that this behaviour survives a complete reinstall, is there perhaps something in the registry that might be relevant? 2. General I'm pretty new to Python, and surprised to find that of all the various Python IDE's only PythonWin works in such a way to take, IMHO proper advantage of Python's dynamic nature. Is PythonWin really unique in that both execution of scripts, and the interactive shell share the same session (there may be a better term than session -context?) I like Komodo for example, but the best it can do is allow you to "interact", in break mode only. Once you script has completed that session is gone. I want to create manipulate, inspect and generally muck about with a set of objects, running scripts against them, debugging and poking at them interactively. I realise you can always execfile manually from a shell but I guess I am expecting the IDE to do this for me when I hit run -and to interact with the debugger when doing so. I suspect PythonWin can only do this because it goes to the trouble of providing its own shell, but I'm guessing here. Is this just not how development tends to go in Python? Or am I missing something fundamental? -thanks for any help on either point Pete F _______________________________________________ Python-win32 mailing list Python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
