Richie Hindle wrote:
Yes, that's what's happened. I've copied the new python24.dll into
C:\python24, and everything now thinks it's 2.4.1c1. Sorry about that.
Is there a reason to keep in c:\python24? Just removing it there should
work as well.
Regards,
Martin
--
http://mail.python.org/mailman/li
[Richie]
> It's possibly that it was an all-users installation but I
> copied the DLL into C:\Python24 for some reason
[Martin]
> Ah, ok. I could not have thought of *that*. That also explains it: the
> upgrading simply did not manage to remove/replace your copy of
> python24.dll.
>
> It's easy
Richie Hindle wrote:
If so, could it
also be that the installer has told you that the target directory
exists, and asked whether you want to proceed anyway?
It probably did, yes.
If this was a true upgrade (allusers to allusers), it didn't ask
the question. It only asks if it thinks this is a fre
[Martin]
> However, I just noticed that the python24.dll is in c:\python24. Could
> it be that you have another one in \windows\system32?
I do, yes.
> If so, could it
> also be that the installer has told you that the target directory
> exists, and asked whether you want to proceed anyway?
It
Brian van den Broek wrote:
A comment about the msi process: even though I set it to install to a
different directory, 2.4.1c1 clobbered my 2.4 install. I remember
reading something somewhere such that I expected this, but a quick
glance at the obvious places for the 2.4.1c1 doesn't produce anyth
Martin v. Löwis said unto the world upon 2005-03-10 20:55:
Anthony Baxter wrote:
On behalf of the Python development team and the Python community, I'm
happy to announce the release of Python 2.4.1 (release candidate 1).
I'd like to encourage feedback on whether the Windows installer works
for peo
Richie Hindle wrote:
I could try again, but maybe there's some useful information you can get
from the partially upgraded environment. Here's how the \python24
directory looks:
I tried to reproduce it, and failed - if the DLL is not in use, it is
updated correctly; if it is in use, a window pops u
Martin v. Löwis wrote:
Vincent Wehren wrote:
is there a reason why msiexec iterates through what looks like all (?)
files and directories in/under the destination directory? There is
massive file I/O going on there (OK, by now you know I didn't
de-install 2.4 before trying ;-)) which explains th
Vincent Wehren wrote:
is there a reason why msiexec iterates through what looks like all (?)
files and directories in/under the destination directory? There is
massive file I/O going on there (OK, by now you know I didn't de-install
2.4 before trying ;-)) which explains the 100% CPU usage and th
Martin v. Löwis wrote:
Anthony Baxter wrote:
On behalf of the Python development team and the Python community, I'm
happy to announce the release of Python 2.4.1 (release candidate 1).
Python 2.4.1 is a bug-fix release. See the release notes at the website
(also available as Misc/NEWS in the source
Richie Hindle wrote:
Gah! I didn't mean to send that. It *didn't* work, as it turns out. It
didn't overwrite python24.dll. It's possible that there was a process
running at the time that was using python24.dll (I have a bunch of
scheduled jobs that run in the background), but the installer didn
[Martin]
> I'd like to encourage feedback on whether the Windows installer works
> for people.
[Me]
> It worked fine for me, upgrading from 2.4 on XPsp2.
Gah! I didn't mean to send that. It *didn't* work, as it turns out. It
didn't overwrite python24.dll. It's possible that there was a proce
Anthony Baxter wrote:
On behalf of the Python development team and the Python community, I'm
happy to announce the release of Python 2.4.1 (release candidate 1).
Python 2.4.1 is a bug-fix release. See the release notes at the website
(also available as Misc/NEWS in the source distribution) for deta
13 matches
Mail list logo
