➜
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.
Created on 2017-02-23 15:46 by aldehoff, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg288455 - (view) | Author: (aldehoff) | Date: 2017-02-23 15:46 | |
This is a revival of issue 1298962 (http://bugs.python.org/issue1298962) from 2009. I can reproduce the problem with an MSI created by cx_Freeze and bdist_msi on a Windows 7 64bit system in a company domain. Python is at version 3.6.0, cx_Freeze is at 5.0.1. I am a user with elevated user rights but not an admin. When installing the MSI, the files are always copied to C:\, whether I have changed the installation directory in GUI or stuck to the default path 'C:\Program Files (x86)\foo'. The program is executable and runs fine. The Uninstaller removes all files without a trace. Following the suggestions from issue 1298962 I have modified the MSI tables in Orca by adding a new Property entry with key 'SecureCustomProperties' and value 'TARGETDIR' fixes the MSI. It now installs into the desired directory. I can reproduce this on multiple builds. |
|||
| msg371261 - (view) | Author: Terry J. Reedy (terry.reedy) *  |
Date: 2020-06-11 11:15 | |
Steve, etc., is this of any current relevance or should it be closed? |
|||
| msg371300 - (view) | Author: Steve Dower (steve.dower) * |
Date: 2020-06-11 16:06 | |
We can close it. bdist_msi isn't recommended for any reason, and cx_Freeze isn't ours. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:43 | admin | set | github: 73819 |
| 2020-06-11 16:06:57 | steve.dower | set | status: open -> closed resolution: out of date messages: + msg371300 stage: resolved |
| 2020-06-11 11:15:22 | terry.reedy | set | nosy:
+ terry.reedy messages: + msg371261 |
| 2017-02-23 15:46:14 | aldehoff | create | |