Hi all, I've noticed a problem with a couple of distutils based installers (py2exe and pywin32) that I think may be a problem in all distutils based windows installers. When you click Next to start the file copy, the Next button is not greyed out or disabled. If you click it again, it seems to start another file copy process running, because you then get an "Overwrite Existing Files?" dialog. If you click Yes, the install may throw a Runtime Error with the message "The process cannot access the file because it is being used by another process..." and it may lock up. I'm running Python 2.3.3 and have seen this in py2exe 0.5.0 and pywin32 build 201. Has anyone else seen this? Thanks, Phil
Phil Rittenhouse <Phil.Rittenhouse@dspfactory.com> writes:
Hi all,
I've noticed a problem with a couple of distutils based installers (py2exe and pywin32) that I think may be a problem in all distutils based windows installers.
When you click Next to start the file copy, the Next button is not greyed out or disabled. If you click it again, it seems to start another file copy process running, because you then get an "Overwrite Existing Files?" dialog. If you click Yes, the install may throw a Runtime Error with the message "The process cannot access the file because it is being used by another process..." and it may lock up.
I'm running Python 2.3.3 and have seen this in py2exe 0.5.0 and pywin32 build 201.
Has anyone else seen this?
I have never tried to press the Next button more than once ;-), but I agree it should be fixed. To help me that I don't forget it, please submit a bug to SF and assign it to me. Thanks, Thomas
participants (2)
-
Phil Rittenhouse -
Thomas Heller