Christopher Brousseau <ch...@surfaceowl.com> added the comment:
First, I'd like to say **thank you** all the work you and the team here do for Python, and Python on Windows. I really appreciate the thoughtful feedback on these ideas. Following up on items in this thread: > do you mean we change "Install launcher for all users" to "Install py > launcher for all users"? yes - that is correct, good clarification > long term comments I see - okay, perhaps we should defer this point to think about it in context of a PR (per below). I really like the idea of not requiring complicated leaps of understanding for every type of user. The main idea I'm thinking about on this first screen: the Default and Customize options are complete/self contained actions - but there there are more choices below that could apply to either Default or Customized installations. When a user clicks on Install Now, the installation starts immediately, so the user may not configure these two checkboxes. The Customize workflow allows the user to back out all the way to the first screen, so it's easy for a user to back up to the beginning if they want to. Maybe this is an order of operations question. Perhaps the checkboxes should be above Install Now or Customize, so there is a linear flow of decisions: configure, then execute. Another idea, using UAC perhaps the Default could be 'install py launcher for all users' and not add to PATH. However, it seems like there may be a few additional requirements. One requirement being Default users need the ability optionally install for all users because of Admin privilege issues, secondly the ability to add Python to PATH. A third requirement is these two choices be available and obvious to both installation paths. Are these correct? > test for admin privileges I did not know that testing for this was not possible - learned something - thanks! >To clarify, we add an "Install py launcher for all users" checkbox on screen 3 >and remove it from screen 2? What gets removed from screen 3 to make space for >it? Correct - that wording seems right. On the space question, it seems like there is space below "Download Debug binaries" so the list from "Associate files" through "Download Debug binaries" could be shifted down without requiring anything to be deleted. > 1. changing current "py launcher" checkbox to "upgrade py launcher" > But this is incorrect. If you don't select the checkbox, you don't get the > launcher. It's a choice to have > or not-have, not a choice to upgrade or > not-upgrade. Got it - I was responding to the grey text below the current checkbox that reads "Upgrades the global py launcher from the previous version". Would it be correct to label this checkbox as "install py launcher"? > other suggestions discussed in this thread. > e.g. 2. moving "for all users" to next line down - looks like we have space, > etc. > This is feasible, but not high priority. PRs welcome. Agree - this is low priority. I will look into doing PR for this, and have to get setup to submit patches etc. so perhaps this is for future release if PR accepted. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37745> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
