Message335779
| Author | chris-k |
|---|---|
| Recipients | chris-k, et, jeremy.kloth, jkloth, ncoghlan, paul.moore, steve.dower, tim.golden, zach.ware |
| Date | 2019-02-17.15:19:53 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1550416793.79.0.809731693913.issue36010@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
for Python 2.7 you can extract the MSI installer (much like a zip file): mkdir "c:\targetdir" msiexec /a "c:\python-2.7.8.amd64.msi" /quiet /norestart TARGETDIR=c:\targetdir msiexec is part of all Windows editions (except for nanoserver). Side note: extracting the MSI does not enable pip. If you need pip, run this on your targetdir: c:\targetdir\python.exe -m ensurepip alternatively, you could perform an unattended installation: msiexec /i "c:\python-2.7.8.amd64.msi" /quiet /norestart Unattended installation also works for Python 3.7: "c:\python-3.7.2-amd64.exe" /quiet InstallAllUsers=1 PrependPath=1 These options worked fine for me in windows containers for CI stuff with servercore. The unattended installation of Python 3.7 also worked fine for me in nanoserver. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-02-17 15:19:53 | chris-k | set | recipients: + chris-k, paul.moore, ncoghlan, tim.golden, jkloth, jeremy.kloth, zach.ware, steve.dower, et |
| 2019-02-17 15:19:53 | chris-k | set | messageid: <1550416793.79.0.809731693913.issue36010@roundup.psfhosted.org> |
| 2019-02-17 15:19:53 | chris-k | link | issue36010 messages |
| 2019-02-17 15:19:53 | chris-k | create | |