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
Hi Roger,
Thanks, I understand it now, I didn't yet receive in the mail any
replies to my post on py-dev when I read your post here! That's why it
didn't make any sense to me.
I didn't yet have a chance to try the workaround given in the
bug-report (remove MBCS encoding line). Hope to find time s
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
In the reply to your post about the crash, there
was a link to the bug report on Sourceforge that
includes a workaround. Specifically, remove the
mbcs encoding tag from the generated file. (or fromg
genpy.py itself so that it never gets put into a new
file) Does this do anything for the unwarrante
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
Hi,
The new installer worked fine for me (WinXP1), but I wasn't sure if I
could install over the old version and have it work properly / remove
the old version from the 'Add / remove programs' list.
It suggested a default location on the C: drive but the old version was
installed on the D: drive
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
Sorry, but I don't know what you mean with 'workaround for the
crash'...
The interpreter no longer crashes when trying to compile this file.
In Python2.4.0 I never saw any syntax error, there was just crash.
Now there is a syntax error, and I when I look at the code I don't spot
it.
regards,
--Ti
[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
[Martin]
> I'd like to encourage feedback on whether the Windows installer works
> for people.
It worked fine for me, upgrading from 2.4 on XPsp2.
The only glitch was that it hung for 30 seconds between hitting Next on
the directory-choosing page and the feature-choosing page.
--
Richie Hindle
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
Does the workaround for the crash do anything for this problem ?
Mark has changed the makepy code to break up long lines, and
a new build of Pywin32 should be out before long.
Roger
"Tim N. van der Leeuw" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi,
>
> I have a
Hi,
I have a problem with Python2.4 and win32com extensions, from Mark
Hammond's win32all package... I posted a few days back about a crash
when compiling files generated by win32com's 'makepy.py' utility.
Now these generated files, which are fine in Python 2.3.5, give a
syntax error on compile.
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 details of
the bugs squis
21 matches
Mail list logo
