PythonWin problems

John Roth newsgroups at
Thu Jan 1 00:58:35 CET 2004

"Colin J. Williams" <cjw at> wrote in message
news:z5GIb.10324$Vl6.2031681 at
> PythonWin has been my favourite IDE for quite a while.
> When one right clicks on a .py file in the Windows Explorer, among the
> options are Open and Edit.  The former is the default and executes
> Python, with the selected script.  The latter activates the PythonWin
> editor, with the selected script.
> Since, most frequently, I wish to edit the script, or execute it with
> the debugger, I tried changing the default to Edit, using the Edit File
> Type menu.
> Unfortunately, this leads to a couple of problems:
> 1. Any activity becomes horrendously slow, and
> 2. The following message appears:
>     LoadBarState failed - LoadBarState failed (with win32 exception!)
> [Dbg]>>>
> Does anyone have a workaround suggestion?

You're going to have to get down and dirty with the registry, I'm

This is the way my registry looks for Python 2.2 (I don't have
2.3 installed yet.) This is in registry patch format which is
imported and exported by regedit.

Windows Registry Editor Version 5.00


@="Python File"








/edit \"%1\""

[HKEY_CLASSES_ROOT\Python.File\shell\Edit with IDLE]

[HKEY_CLASSES_ROOT\Python.File\shell\Edit with IDLE\command]

C:\\PROGRA~1\\PYTHON22\\Tools\\idle\\idle.pyw -e \"%1\""



@="C:\\PROGRA~1\\PYTHON22\\python.exe \"%1\" %*"

[end of registry patch]

Restore yours to look something like this (and make sure you
don't put my values into your system - they probably won't work!)

Once you do that, change (or add) the default value of the


key to say "Edit".

That's all there is to it. Remember to back up your registry
first, or at least save the key your playing with.

If you're reluctant to get that close to the registry,
there are a large number of resources on the net,
and I heartily recommend "Windows XP annoyances"
by David Karp (O'Reilly). The information on file types and
associations is the same for all Windows versions.

John Roth

> Thanks.
> Colin W.

More information about the Python-list mailing list