KeyWeeUsr added the comment:
python-3.5.2.exe /layout <folder>
11.01.2017 19:30 <DIR> .
11.01.2017 19:30 <DIR> ..
11.01.2017 19:30 3 035 136 core_d.msi
11.01.2017 19:30 2 240 512 core_pdb.msi
11.01.2017 19:30 98 304 dev_d.msi
11.01.2017 19:30 110 592 exe_d.msi
11.01.2017 19:30 102 400 exe_pdb.msi
11.01.2017 19:30 5 378 048 lib_d.msi
11.01.2017 19:30 4 820 992 lib_pdb.msi
29.10.2016 11:13 29 269 656 python-3.5.2.exe
11.01.2017 19:30 1 179 648 tcltk_d.msi
11.01.2017 19:30 139 264 tcltk_pdb.msi
11.01.2017 19:30 331 776 test_d.msi
11.01.2017 19:30 286 720 test_pdb.msi
12 File(s) 46 993 048 bytes
2 Dir(s) 1 245 736 960 bytes free
---
msiexec /a exe_d.msi targetdir=%cd%\<folder>
Msiexec window has title "Python 3.5.2 Executables (32-bit debug)" and the
targetdir contains:
11.01.2017 19:36 <DIR> .
11.01.2017 19:36 <DIR> ..
25.06.2016 21:57 51 712 pythonw_d.exe
25.06.2016 21:57 364 544 pythonw_d.pdb
25.06.2016 21:57 51 712 python_d.exe
25.06.2016 21:57 364 544 python_d.pdb
4 File(s) 832 512 bytes
2 Dir(s) 1 264 963 584 bytes free
Notice, that everywhere is "_d" I talk about so much.
> ...and puts them in a location where they will be used later without
> redownloading...
Yes, in a state that only the EXE installer is able to use them.
> *hypothetical*
msiexec /a python-2.7.13.msi targetdir=%cd%\<folder>
11.01.2017 19:45 <DIR> .
11.01.2017 19:45 <DIR> ..
11.01.2017 19:45 <DIR> DLLs
11.01.2017 19:45 <DIR> Doc
11.01.2017 19:45 <DIR> include
11.01.2017 19:45 <DIR> Lib
11.01.2017 19:45 <DIR> libs
17.12.2016 20:49 38 591 LICENSE.txt
17.12.2016 20:34 474 595 NEWS.txt
11.01.2017 19:45 835 584 python-2.7.13.msi
17.12.2016 20:44 27 136 python.exe
17.12.2016 20:43 2 639 872 python27.dll
17.12.2016 20:44 27 648 pythonw.exe
03.12.2016 21:01 56 938 README.txt
11.01.2017 19:45 <DIR> tcl
11.01.2017 19:45 <DIR> Tools
17.12.2016 20:44 111 104 w9xpopen.exe
8 File(s) 4 211 468 bytes
9 Dir(s) 1 162 199 040 bytes free
Fully usable, portable and working Python interpreter for Python installers
<3.5.0 without a single beep about admin rights (kivy, numpy, scipy, cython,
mingwpy, etc.). With some workaround probably even usable for ALLUSERS=1, but
I'm not going to try that on my system.
How is Debug installer not an issue/bug in a Python Release? Am I missing
something or is it ok to unpack Debug installers from an official installer and
not the actually used ones, the ones that produce Release that works?
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29231>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
