I use the *.msi installers for python to automate deployment of... an absurd number of python installations.  I have been able to do this relatively easily, as the Windows installer didn't change much between 2.6 and 3.4 (possibly much longer than that, but I don't know about 2.5 or earlier).

3.5 added a new installer (the web installer), and apparently dropped the old standby *.msi installers, for the beta versions.

Will there be *.msi installers for 3.5?

There's an "executable installer"; it's a .exe instead of a .msi.

Also have a read of https://docs.python.org/3.5/using/windows.html and see whether it will suit your needs. I need to hear feedback on this, as we're running short on time to make drastic changes if they are necessary.

I too automate installation of absurd numbers of Python interpreters (across versions rather than machines, but still fairly often), and I haven't had any trouble being able to install 3.5 in a very similar way.

Related to the exe installer... /? lists only 4 options, none of which are useful in restricting the installation, or changing its location.

and...you already addressed that.  Ignore previous.

Having now worked with the new installer, there is nothing wrong with it, and provides sufficient scritpability, if that is a word.  I only have two (and a half) thoughts on it:

1. This should be more prominently documented.  The addition of the new web installer is listed in What's New, but not that the change to the new installer, and lack of the old msi installer.  This is noteworthy for anyone who does scripted installs of python.

2. passing /? should list the available kay-value arguments.

2.5. The help should really be to stdout... If you are running /? on an installer executable, you are in the command prompt - no one creates a shortcut to an installer exe then modifies that shortcut to add the /? argument.

> 1. This should be more prominently documented.

Very true. I'll get a link to the updated docs page in there.

> 2. passing /? should list the available kay-value arguments.

Should be doable. I've mostly been holding off until I stop changing the arguments. At the very least, I can add a link to the doc page from here as well.

> 2.5. The help should really be to stdout...

Unfortunately, I don't think this one is possible as the installer is SUBSYSTEM:WINDOWS not CONSOLE. stdout is unbound by default, and the only way to bind it is to open a new console window, which doesn't really help here. Switching to SUBSYSTEM:CONSOLE is going to open a new console window every time you run it (and running by double-clicking or from a browser will be the vast majority).

I can probably add a link from the front page of the installer to bring up the help page, but I wouldn't want it to be too obtrusive (maybe from the Customize Options page?) - the aim is to reduce the number of decisions for most users by having a very clean front page.

There was a suggestion a while ago to generate a full command line based on the options selected in the UI, which is doable, but maybe not useful enough to justify the time and effort. I'd expect anyone capable of this sort of deployment to be able to figure out the command line for themselves though, given access to the list of possible options.

New changeset 06600287f11f by Steve Dower in branch '3.5':
Issue #24642: Adds installer notes and links to What's New for 3.5
https://hg.python.org/cpython/rev/06600287f11f

New changeset d6c91b8242d2 by Steve Dower in branch 'default':
Issue #24642: Adds installer notes and links to What's New for 3.5
https://hg.python.org/cpython/rev/d6c91b8242d2

on 2.5, I figured the answer would be along those lines.

for 2, Linking to the documentation at least would be helpful (or otherwise indicating that there are arguments that are not listed and are in the docs) if the arguments cant be listed reasonably easily.

New changeset 9f60ec6d6586 by Steve Dower in branch '3.5':
Issue #24642: Improves help text displayed in the Windows installer.
https://hg.python.org/cpython/rev/9f60ec6d6586