Paul answered sufficiently for the venv part, but I wanted to address this point.
On 09Sep2019 0621, Kyle Stanley wrote:
+1, Particularly on this part. If the user installing Python has administrative access, I don't see much of a reason for them to have to install a separate launcher and installation. Recommending a global py.exe install for them seems to be far more straight forward.
I'm not certain as to whether or not we are able to collect statistics on this, but I would not be at all surprised if the majority of users installing Python had administrative access on the device they're installing it on. While I think the ability to allow non-admin users to install packages in their own install is very useful, it should not come at the expense of making the process confusing for those with administrative privileges.
User with administrative privileges are by implication better able to handle decisions such as this. If they are not, they should not be administrating a machine.
Anecdotally (since it's very hard to collect demographic data here), the majority of Python users under the age of 18 do not have administrative privileges. You are literally saying that these kids should be given a harder time installing Python than someone who owns and maintains their own machine. Forgive me for disagreeing with you.
As I said on the bug related to this (https://bugs.python.org/issue37745), I'm happy to accept patches to improve the wording. I'm also willing to consider changing the default option for clean installs to not install the launcher for All Users (basically flip that checkbox, and perhaps remove it from the front page).
But the flow of the installer has I believe proven itself well with a broad range of users. Nothing in this thread has come anywhere near suggesting otherwise with anything like the feedback I've heard from users.