[issue29231] Broken MSIs in Python 3.5+

2017-01-11 Thread KeyWeeUsr
KeyWeeUsr added the comment: > Ah, you're using the full installer, which has the non-debug versions > embedded and therefore does not ever need to download them. Hm, makes sense now, however, isn't that a bug? I mean, even if it's embeded... I'm just curious ^^ &

[issue29231] Broken MSIs in Python 3.5+

2017-01-11 Thread KeyWeeUsr
KeyWeeUsr added the comment: python-3.5.2.exe /layout 11.01.2017 19:30 . 11.01.2017 19:30 .. 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:3098 304 dev_d.msi 11.01.2017 19:30 110

[issue29231] Broken MSIs in Python 3.5+

2017-01-11 Thread KeyWeeUsr
KeyWeeUsr added the comment: Re blog post "Why are there so many Python installers?" > As a result, the old installer always requires administrative privileges just > in case you choose to install for all users. This prevents installation of > Python on machines where y

[issue29231] Broken MSIs in Python 3.5+

2017-01-10 Thread KeyWeeUsr
Changes by KeyWeeUsr : -- versions: +Python 3.6 ___ Python tracker <http://bugs.python.org/issue29231> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29231] Broken MSIs in Python 3.5+

2017-01-10 Thread KeyWeeUsr
New submission from KeyWeeUsr: In versions _lower_ than 3.5.0 there was a `.MSI` installer for Windows, which had a really nice hidden option. That option looked like this: msiexec.exe /a "file.msi" /qb /L*V "file.log" ALLUSERS=0 TARGETDIR="target" C