<div class="gmail_quote">On Mon, Nov 14, 2011 at 2:08 PM, Wayne Watson <span dir="ltr"><<a href="mailto:sierra_mtnview@sbcglobal.net">sierra_mtnview@sbcglobal.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I had py 2.5.2 installed (Yes, I know it's old) on my Win 7 64-bit PC earlier this year, but it began to fail back in June. I tried a uninstall/install, but that got me nowhere. I tried again yesterday. Uninstalled, then puzzled over whether I should delete the remaining python25 folder. There were a few files in it. Nothing that looked relevant of use any longer. I did notice several Remove....exe files for numpy, scipy and others. Rather than chance messing up python25, I renamed it, then installed 2.5.2.<br>
<br>
I found that every time I tried to activate a py file, or open it in IDLE, I would get an error that said something like this:<br>
c:\Users\blah\...\junk.py is not a valid Win 32 app. (or idle.pyw)<br>
<br>
Comments?<br>
<br></blockquote><div>Sounds like a problem with Windows' file associations / default programs settings. <br>Go to Control Panel / Programs / Default Programs / Set your default programs. I'm guessing that ".py" and ".pyw" are still set to be opened by a Python installation that isn't there anymore. Fix that, and you should be golden.<br>
</div></div><br>