[issue21427] installer not working

Peter Santoro added the comment: I believe I may have hit a related issue yesterday. I'm using Python 3.3.5 (32 and 64 bit) and 3.4.1 (32 and 64 bit) releases all on the same Windows 7SP1/64bit PC (patched with latest MS updates). The Tkinter applications that I wrote and have been using wit

[issue21427] installer not working

Uwe added the comment: problem is solved observation - installer problem only occurred on win7 32 bit with prior python installation (my working system) - When repeating the installer problem I noticed that a window was opened very shortly with python.exe running. An error message from this cal

[issue21427] installer not working

Uwe added the comment: the installer went 2/3 through the process and was installing already something in the default dir c:\Python34 Then after a small pause the error message was shown and the installer removed all the files leaving an empty ..\lib in the default dir The behavior is quite rep

[issue21427] installer not working

Martin v. Löwis added the comment: That the removal of 3.4 removes py.exe despite 3.3 still being installed is easy to explain: the registration of the reference counter failed, hence the file was not reference counted, and the first removal decided to remove it (there being no reference count

[issue21427] installer not working

Zachary Ware added the comment: Here's the log, and some notes: Starting state: - Python 3.3.5 installed to P:\Python33 - Python 3.4.1 installed to P:\Python34 - py[w].exe present in C:\Windows State after Python 3.4.1 uninstalled by python-3.4.1.msi (and manually removed P:\Python34 which sti

[issue21427] installer not working

Martin v. Löwis added the comment: Zachary: It "shouldn't" work for you, given this report. Please run msiexec /i /l*v py.log and attach the (possibly compressed) py.log. Verify that it actually did install py.exe into c:\windows. -- ___ Python t

[issue21427] installer not working

Steve Dower added the comment: That reasoning makes sense. I don't see any other way to achieve the same thing without requiring a newer version of Windows Installer on the machine (msidbComponentAttributesDisableRegistryReflection requires 4.0). Having a second component for 32-bit OS may be

[issue21427] installer not working

Zachary Ware added the comment: Martin v. Löwis wrote: > I never got to test this out of lack of a 32-bit Windows installation, > apparently, it doesn't work. It does work on my 32-bit machine, though; I have had no issues installing 32-bit Python 3.3 or 3.4 on 32-bit Windows 7 Pro. If there's

[issue21427] installer not working

Martin v. Löwis added the comment: Here is the rationale: 1. py.exe is a 32-bit binary installed into C:\windows, see PEP 397. It's in C:\windows so that it will be on the path for both 32-bit and 64-bit processes. 2. py.exe is installed by multiple installers (both 32-bit and 64-bit, and mult

[issue21427] installer not working

Terry J. Reedy added the comment: I think what Steve meant is that *if* the 32-bit installer is working right, then it should be the default because it would then work for everyone, while the 64-bit installer cannot possibly work for people with 32-bit windows. --

[issue21427] installer not working

Uwe added the comment: not sure what you mean: the installer for 64 bit is working fine the installer for 32 bit is not working - this is true also for the new version 3.4.1 for those who may try: compiling is tricky with VC2010 pro -- ___ Python tra

[issue21427] installer not working

Steve Dower added the comment: eryksun's analysis is correct. If the component is marked 64-bit then it will not install on a 32-bit OS. This needs to be switched for the 32-bit installer. (I also don't see why you'd want to set the 64-bit SharedDLLs key for a 32-bit DLL. Is there some reason

[issue21427] installer not working

Mark Lawrence added the comment: FWIW I've never had any installation problems involving py.exe. -- nosy: +BreamoreBoy ___ Python tracker ___

[issue21427] installer not working

Zachary Ware added the comment: Nosy-ing the Windows installer experts; I haven't had any problems with this and am not familiar with the MSI library or tool. -- nosy: +loewis, steve.dower ___ Python tracker _

[issue21427] installer not working

Terry J. Reedy added the comment: I compile 32 bit debug binaries from repository with the free VC++ express 2010. I presume the 'install' option works. -- nosy: +terry.reedy ___ Python tracker ___

[issue21427] installer not working

Uwe added the comment: I guess this is merely describing the problem and not the solution? (by the way I had no difficulties with the 64bit version on a 64bit win7 system) Would it be possible to produce the binairies myself using the mingw compiler? The readme says visual c++ is required. ---

[issue21427] installer not working

eryksun added the comment: This is the first time I've used msilib, but it does appear that the component is marked as 64-bit: >>> import msilib >>> msidbComponentAttributes64bit = 256 >>> sql = ("SELECT ComponentId,Attributes FROM Component " ..."WHERE Component='launch

[issue21427] installer not working

Ned Deily added the comment: There are two different names: the 64-bit installer is python-3.4.0.amd64.msi. But I see now that the error refers to py.exe, which I believe is the Python launcher. I've nosyed the Windows experts. -- nosy: +tim.golden, zach.ware ___

[issue21427] installer not working

Uwe added the comment: Of course, only official sources the file is named python-3.4.0.msi and 23,924KB the name is similar to that of earlier versions which worked fine So I am not sure, whether it is 32 or 64bit maybe it would be a good idea to use two different names such as x86 and x64?

[issue21427] installer not working

Ned Deily added the comment: Did you try using the 32-bit (x86) installer from https://www.python.org/downloads/release/python-340/ ? Unfortunately, I believe the default download button currently only downloads the 64-bit version. -- nosy: +ned.deily

[issue21427] installer not working

New submission from Uwe: Installer fails to install 3.4 on win7 32 bit Error: cannot register 64 bit component {BE22BD81-ECE5-45BD-83B8-84BA45846A2D} on 32 bit system. KeyPath: C:\Windows\py.exe -- messages: 217878 nosy: ellipso priority: normal severity: normal status: open title: inst