New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
msi installs to the incorrect location (C drive) #46524
Comments
When installing Python using any of the following stand-alone installers: python-2.5.2.amd64.msi all the files and folders are installed in C:\ instead of C:\Python25\ |
Please run msiexec /i <msi> /l*v python.log Compress the log, and attach it to this report. |
log now attached |
Checking Progress. This is a big of a show-stopper as it prevents me |
No progress so far; may not proceed at all during April (IOW, I haven't Contributions are welcome. |
As a further follow-up, I have now looked at the log file, and the MSI (s) (DC:40) [10:44:39:425]: Ignoring disallowed property TARGETDIR Try setting SecureCustomProperties (through orca.exe) and report whether |
using Orca, I modified the .msi file and python now appears to be Property -> SecureCustomProperty Running the modified .msi file resulted in Python being installed in |
Apparent duplicates are at http://bugs.python.org/issue1298962 and I can duplicate this problem with the MSI installers for Python 2.4.4, I've attached two logs from a Python 2.6b1 install on Windows XP, one Adding at least TARGETDIR to the SecureCustomProperties with Orca allows I'd be happy to provide any more information that can help get this |
Contribution of a patch would be the best way to resolve this quickly. |
I also have this problem. (2.5 msi installer under Win2K with a non- Searching the web I found this posting from 2005 That poster created an SF bug report which is now bpo-1298962. He
That describes exactly my situation. The solution is, apparently:
which Martin reported here. Martin suggested using orca, but I have no I know this is pretty much a "me too" report. I'm doing so to say that I would like to see this fixed before 2.6 is released. All I can do to |
Please try out the file at http://www.dcl.hpi.uni-potsdam.de/home/loewis/python-2.6.14106.msi and report whether it fixes the issue. |
Yes, that installed Python 2.6 into the correct location (C:\Python26 |
Fixed in r66305. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: