[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 ^^ > If you start from the web in

[issue29231] Broken MSIs in Python 3.5+

2017-01-11 Thread Paul Moore
Paul Moore added the comment: > Fully usable, portable *and unsupported* - you apparently ignored that point from Steve's comment > and working Python interpreter That's (essentially) pure luck. I don't think I've ever seen any suggestion that the /a flag for *any* MSI installer (Python or oth

[issue29231] Broken MSIs in Python 3.5+

2017-01-11 Thread Steve Dower
Steve Dower 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. If you start from the web installer, it will download the MSIs for the non-debug components as well. But as I said, you're in totally

[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 Steve Dower
Steve Dower added the comment: "msiexec /a" does not install anything - it converts the MSI into a source layout for lazy network installs. It is, and always has been, completely unsupported as an approach to installing Python, and we are under no obligation to maintain it. Copy-pasting the i

[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 you do not have full cont

[issue29231] Broken MSIs in Python 3.5+

2017-01-11 Thread Steve Dower
Steve Dower added the comment: I discussed installers on my blog at http://stevedower.id.au a while back. There are some other options linked from there, and also rationale for why things are how they are. -- ___ Python tracker

[issue29231] Broken MSIs in Python 3.5+

2017-01-10 Thread KeyWeeUsr
Changes by KeyWeeUsr : -- versions: +Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[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" CURRENTDIRECTORY="%cd%" which basically