[issue1565509] Repair or Change installation error

Zachary Ware added the comment: Steve Dower wrote: > I vote to close. +1, and done. -- assignee: loewis -> resolution: -> third party stage: test needed -> resolved status: open -> closed ___ Python tracker __

[issue1565509] Repair or Change installation error

Steve Dower added the comment: Newer versions of Windows Installer (this looks like an XP issue...) will preserve a copy of the original MSI in a safe place, so this problem should not occur any more. I vote to close. -- ___ Python tracker

[issue1565509] Repair or Change installation error

Mark Lawrence added the comment: I don't recall ever seeing a problem like this, but then I haven't used IE in years and don't intend using it now just for this. -- components: +Windows nosy: +BreamoreBoy, steve.dower, zach.ware versions: +Python 3.4, Python 3.5 -Python 3.1, Python 3.2

[issue1565509] Repair or Change installation error

Changes by Mark Lawrence : -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6, Python 3.0 ___ Python tracker ___ ___ Pytho

[issue1565509] Repair or Change installation error

Tim Golden added the comment: Well it may be uncommon, but it's perfectly easily reproducible: Just try to reinstall / repair from a file not called python-2.5.2.msi. Maybe uninstall: haven't tried. If Martin doesn't get there, I'll try to look at the log and see if there's something straightf

[issue1565509] Repair or Change installation error

Daniel Diniz added the comment: Greg, I've never seen this problem being reported by another user, so ISTM it's fair to use 'uncommon' (as in 'rarely occurring or appearing, infrequent, occasional, unusual') to refer to it. Also, AFAIK, 'Repair or Change' is rarely reliable. But I agree that if

[issue1565509] Repair or Change installation error

Greg Hazel added the comment: IE renamed the file for me. So this is not uncommon. -- status: closed -> open ___ Python tracker ___ ___

[issue1565509] Repair or Change installation error

Daniel Diniz added the comment: If Greg's diagnostic is correct, then it's either a WFM (uncommon use case) or a matter of hard-coding the installer file name. Closing as WFM, reopen if necessary. -- nosy: +ajaksu2 priority: normal -> low resolution: -> works for me stage: -> test ne