This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Windows installation problem with 3.3.5
Type: behavior Stage:
Components: Installation, Windows Versions: Python 3.3
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: BreamoreBoy, loewis
Priority: normal Keywords:

Created on 2014-03-10 09:43 by BreamoreBoy, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (3)
msg213019 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2014-03-10 09:43
The upgrade from 3.3.4 to 3.3.5 has removed py[w].exe from c:\windows.  Tim Golden has given a possible explanation here
msg213020 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2014-03-10 09:50
I don't think Tim's theory is true, but I can't suggest a better explanation. This would need to be debugged, by running 

msiexec /i name-of-installer.msi /l*v python.log

and submitting the resulting python.log here.
msg213033 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2014-03-10 14:22
I did this.  Install 3.4.0.rc3 and check that the py[w].exe files were in c:\windows.  Uninstall 3.3.5, the py[w].exe files had been deleted.  Reinstall 3.3.5, py[w].exe were in c:\windows but I noticed that they were different sizes from the 3.4 versions.  The log output shows "MSI (s) (A8:84) [14:05:32:170]: File: C:\Windows\py.exe; To be installed;	Won't patch; No existing file" and similar for pyw.exe.  I'm not sure if this is worth chasing, maybe leave it open for a couple of weeks just in case anyone else complains, if not close?
Date User Action Args
2022-04-11 14:57:59adminsetgithub: 65079
2014-06-20 14:01:23BreamoreBoysetstatus: open -> closed
2014-03-10 14:22:33BreamoreBoysetmessages: + msg213033
2014-03-10 09:50:34loewissetnosy: + loewis
messages: + msg213020
2014-03-10 09:43:05BreamoreBoycreate