When I upgraded to wxPython 2.5.4 (Windows XP machine), I decided not to un-install wxPython 2.5.3 first to see how the Multi-version install would work. Here's the steps I took and the results:
1. Ran 2.5.4 installer. I noticed it didn't ask me about uninstalling the old version. I left "make this version the default checked" so that it would become default.
2. When I ran the wxPython demo, it used 2.5.3 instead of 2.5.4. (The demo doesn't seem to use wxversion, so I assumed 2.5.3 was still default.)
3. Went into Add/Remove Programs. Only wxPython 2.5.4 was in the list, no 2.5.3. (It was there before the 2.5.4 install - I checked while I was debating uninstalling first.)
4. Went into C:\Python23\lib\site-packages. There was a wx-2.5.3-ansi build here. Went into it, and ran the uninstaller.
5. Re-ran demo - 2.5.4 now loads and runs.
Is anyone else seeing similar results, or is it just my machine that's having problems? I'm not sure if my machine got goofed up somehow, but I thought I'd report this and see if anyone else can reproduce it.
When I upgraded to wxPython 2.5.4 (Windows XP machine), I decided not to un-install wxPython 2.5.3 first to see how the Multi-version install would work. Here's the steps I took and the results:
1. Ran 2.5.4 installer. I noticed it didn't ask me about uninstalling the old version.
As expected, it only checks in the versioned directory for an existing install. So if there was a 2.5.4.2 release then when you install it you'll be asked if you want to uninstall the other one first.
I left "make this version the default checked" so that
it would become default.
2. When I ran the wxPython demo, it used 2.5.3 instead of 2.5.4. (The demo doesn't seem to use wxversion, so I assumed 2.5.3 was still default.)
Hmm... It must not have overritten the wx.pth file. I thought that I had tested that. I'll check again.
3. Went into Add/Remove Programs. Only wxPython 2.5.4 was in the list, no 2.5.3. (It was there before the 2.5.4 install - I checked while I was debating uninstalling first.)
This is an InnoSetup thing, it notices that they are the same software and installed to the same place (site-pacakges) and so removes the old entry from the registry. I think I tried to work around this before but I'm not sure what roadblocks I ran into or why I decided to leave it as is... Once we move to 2.6 then it will treat 2.5 and 2.6 as separate and will leave both entries in the Add/Remove Programs list.
4. Went into C:\Python23\lib\site-packages. There was a wx-2.5.3-ansi build here. Went into it, and ran the uninstaller.
5. Re-ran demo - 2.5.4 now loads and runs.
Did you happen to look at the contents of the wx.pth file before and after you uninstalled the 2.5.3 version? I'd like to figure out why 2.5.4 wasn't the default before.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Hi all,
When I upgraded to wxPython 2.5.4 (Windows XP machine), I decided not to un-install wxPython 2.5.3 first to see how the Multi-version install would work. Here's the steps I took and the results:
1. Ran 2.5.4 installer. I noticed it didn't ask me about uninstalling the old version.
As expected, it only checks in the versioned directory for an existing install. So if there was a 2.5.4.2 release then when you install it you'll be asked if you want to uninstall the other one first.
OK, I just wanted a confirm on that.
I left "make this version the default checked" so that
it would become default.
2. When I ran the wxPython demo, it used 2.5.3 instead of 2.5.4. (The demo doesn't seem to use wxversion, so I assumed 2.5.3 was still default.)
Hmm... It must not have overritten the wx.pth file. I thought that I had tested that. I'll check again.
3. Went into Add/Remove Programs. Only wxPython 2.5.4 was in the list, no 2.5.3. (It was there before the 2.5.4 install - I checked while I was debating uninstalling first.)
This is an InnoSetup thing, it notices that they are the same software and installed to the same place (site-pacakges) and so removes the old entry from the registry. I think I tried to work around this before but I'm not sure what roadblocks I ran into or why I decided to leave it as is... Once we move to 2.6 then it will treat 2.5 and 2.6 as separate and will leave both entries in the Add/Remove Programs list.
I'll try and look into this myself soon. I'm actually playing with the Inno backend for PyPackager right now, ironically enough support for registry keys. (Hey, I'm slow, but I never abandon things!) I'm hoping to keep hammering on it and have something for alpha in the next few weeks. I've also got prelim deb and rpm backends and I'm working to create an OS X backend (at least an app bundle backend as a start, and later a pkg backend too) as I want to create a Documancer app bundle on OS X and I figure rather than doing all the manual work of making scripts for each platform over and over, I might as well take this opportunity to have some fun.
4. Went into C:\Python23\lib\site-packages. There was a wx-2.5.3-ansi build here. Went into it, and ran the uninstaller.
5. Re-ran demo - 2.5.4 now loads and runs.
Did you happen to look at the contents of the wx.pth file before and after you uninstalled the 2.5.3 version? I'd like to figure out why 2.5.4 wasn't the default before.
No, on hindsight it was an obvious thing to do, but I didn't give it much thought at the time. ;-/ I could try repeating the process starting with the 2.5.3 install, but I want to be sure wxMozilla is working with 2.5.4 before I do that.
Thanks,
Kevin
···
On Mar 22, 2005, at 4:43 PM, Robin Dunn wrote:
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org
(Hey, I'm slow, but I never abandon things!) I'm hoping to keep hammering on it and have something for alpha in the next few weeks. I've also got prelim deb and rpm backends and I'm working to create an OS X backend (at least an app bundle backend as a start, and later a pkg backend too) as I want to create a Documancer app bundle on OS X and I figure rather than doing all the manual work of making scripts for each platform over and over, I might as well take this opportunity to have some fun.