Using the control panel launcher should launch the version of python
that is associated with .pyw files. PYTHONHOME will only affect where
it finds the library. I can't think of anything that could possibly
cause this that would be fixed by re-installing wx.
Note that changing environment variables in the control panel doesn't
update currently running processes. If you tried to run something from
the same command window, it would still have had the old PYTHONHOME
set.
···
On 9/5/07, Tony Cappellini <cappy2112@gmail.com> wrote:
I believe I know how I corrupted my wx installation.
In Ctrl panel, My the path to my current python installation is set like this
C:\stuff;%PYTHONHOME%;C:\OtherStuff
PYTHONHOME=C:\Python25I frequently need to go back and forth between python 2.4 & 2.5, but
at the moment, I only have wx installed for 2.5.When I switch between python versions, sometimes I do this only in a
console window by typing PYTHONHOME=C:\Python24, so the change goes
away when the console closes.Last night when I was working on a 2.4 project, I went to control
panel and changed PYTHONHOME=C:\Python24 in the system wide
environment variableToday, without restoring PYTHONHOME to 2.5, I launched PaAlaMode, but
it never displayed itself. I then tried the wx Demo launcher-same
problem.I then remembered I had switched PYTHONHOME to Python2.4, so I
switched the environment variable back to python2.5, but now my wx
installation is corrupt. No wx programs run.I have no choice but to re-install wx.
Short of remembering to restore the control panel variable back to
2.5, is there a better way to deal with multiple versions of Python
installations and multiple versions of wx?