Re: RELEASED Python 2.4.2 (final)

2005-10-02 Thread Martin v. Löwis
Bugs wrote: > - I had an old ActiveState python24.dll in \windows\system32 which I > deleted. That must've been left over from a 2.4.1 ActiveState > installation which I had installed then uninstalled sometime ago. > > - I then uninstalled Python 2.4.2 and re-installed it for "all" users. > After

Re: RELEASED Python 2.4.2 (final)

2005-09-30 Thread Bugs
- I had an old ActiveState python24.dll in \windows\system32 which I deleted. That must've been left over from a 2.4.1 ActiveState installation which I had installed then uninstalled sometime ago. - I then uninstalled Python 2.4.2 and re-installed it for "all" users. After that everything seeme

Re: RELEASED Python 2.4.2 (final)

2005-09-30 Thread Martin v. Löwis
Trent Mick wrote: > I suppose that is possible. Martin, does python-2.4.2.msi install > python24.dll to the Python install dir for a "per-user" installation? Yes, that is supported. It would be good if Bugs could confirm that he only deleted the wrong python24.dll, with the proper one being insta

Re: RELEASED Python 2.4.2 (final)

2005-09-30 Thread Trent Mick
[Fuzzyman wrote] > I had problems updating from activestate 2.4 to activestate 2.4.1 > > I think it was caused by not uninstalling the original. This does mean > that even a *minor* version upgrade is a PITA. To do it cleanly all > extension modules have to be uninstalled and re-installed. > > *s

Re: RELEASED Python 2.4.2 (final)

2005-09-30 Thread Trent Mick
[Peter Hansen wrote] > Couldn't it also happen if the first time someone did an "admin" install > which (I believe) puts the DLLs in the system folder, and the next time > did just a non-admin install which doesn't do that? (Or am I > misunderstanding the conditions under which c:\windows\syste

Re: RELEASED Python 2.4.2 (final)

2005-09-30 Thread Peter Hansen
Martin v. Löwis wrote: > Trent Mick wrote: > >>It is possible that the python.org installer didn't overwrite the >>"python24.dll" in the system directory (C:\WINDOWS\system32). Try doing >>this: > > > Even though this is apparently what happened, I'm puzzled as to why it > happened: shouldn't th

Re: RELEASED Python 2.4.2 (final)

2005-09-30 Thread Steve Holden
Fuzzyman wrote: > On Thu, 29 Sep 2005 17:53:47 -0700, Bugs <[EMAIL PROTECTED]> wrote: > > >>I downloaded the 2.4.2 Windows Binary Installer from python.org but when >>I try to run python.exe I get the following in the console: >> >>ActivePython 2.4.1 Build 247 (ActiveState Co

Re: RELEASED Python 2.4.2 (final)

2005-09-30 Thread Fuzzyman
On Thu, 29 Sep 2005 17:53:47 -0700, Bugs <[EMAIL PROTECTED]> wrote: >I downloaded the 2.4.2 Windows Binary Installer from python.org but when >I try to run python.exe I get the following in the console: > >ActivePython 2.4.1 Build 247 (ActiveState Corp.) based on >Python 2.4.1

Re: RELEASED Python 2.4.2 (final)

2005-09-30 Thread Steve Holden
Delaney, Timothy (Tim) wrote: > Bugs wrote: > > >>It says ActivePython 2.4.1 but I downloaded the 2.4.2 binary installer >>from python.org and the python.exe executable I'm running is >>timestamped 9/28/2005 12:41PM... Any ideas what I'm doing wrong? > > > Visit this site: > http://www.catb.or

Re: RELEASED Python 2.4.2 (final)

2005-09-29 Thread Martin v. Löwis
Trent Mick wrote: > It is possible that the python.org installer didn't overwrite the > "python24.dll" in the system directory (C:\WINDOWS\system32). Try doing > this: Even though this is apparently what happened, I'm puzzled as to why it happened: shouldn't the version number of python24.dll in t

Re: RELEASED Python 2.4.2 (final)

2005-09-29 Thread Bugs
Thanks Trent, you called it, it was an errant python24.dll left over from an old ActiveState installation. Trent Mick wrote: [snip] > > It is possible that the python.org installer didn't overwrite the > "python24.dll" in the system directory (C:\WINDOWS\system32). Try doing > this: > [snip] --

Re: RELEASED Python 2.4.2 (final)

2005-09-29 Thread Trent Mick
[Bugs wrote] > I downloaded the 2.4.2 Windows Binary Installer from python.org but when > I try to run python.exe I get the following in the console: > > ActivePython 2.4.1 Build 247 (ActiveState Corp.) based on > Python 2.4.1 (#65, Jun 20 2005, 17:01:55) [MSC v.1310 32 bit (I

RE: RELEASED Python 2.4.2 (final)

2005-09-29 Thread Delaney, Timothy (Tim)
Bugs wrote: > It says ActivePython 2.4.1 but I downloaded the 2.4.2 binary installer > from python.org and the python.exe executable I'm running is > timestamped 9/28/2005 12:41PM... Any ideas what I'm doing wrong? Visit this site: http://www.catb.org/~esr/faqs/smart-questions.html Then try run

Re: RELEASED Python 2.4.2 (final)

2005-09-29 Thread Bugs
I downloaded the 2.4.2 Windows Binary Installer from python.org but when I try to run python.exe I get the following in the console: ActivePython 2.4.1 Build 247 (ActiveState Corp.) based on Python 2.4.1 (#65, Jun 20 2005, 17:01:55) [MSC v.1310 32 bit (Intel)] on win32 Type "