[issue37745] 3.8b3 - windows install gui/ inconsistent options
New submission from Christopher Brousseau : When installing 3.8.0b3 64-bit into Win 10 using the gui following the `customize installation` path, there are duplicate and inconsistent options on three different screens for the `install for all users` checkbox. Observed Behavior: 1. first screen (Install Python) - `install launcher for all users` is marked as checked as default 2. second screen (Optional Features) - 2.1 `for all users` is also marked as checked if first screen marked. if second screen marked - this is unchecked. 2.2 layout of this checkbox is above a comment that relates only to the "py launcher" checkbox. would be more clear for user if `for all users` was located below "py launcher", or removed from this screen (per note below) 3. third screen (Advanced Options) - `Install for all users` is UNchecked in all cases, even if first & second screens are checked. Expected Behavior: 1. if first screen is checked, all follow on screens are also checked 2. feature options only appear on one screen, or at a minimum, checkbox label is exactly the same on all screens Additional Questions for the team: 1. Should all install customizations be removed from first screen, set as default options and just listed as descriptions under the `Install Now` default? 2. Should `for all users` option be removed from the 2nd screen (Optional Features)? It seems more like an "advanced option" than a feature. Screenshots (this site appears to only allow one file) first: https://imgur.com/a/0a45CBh second: https://imgur.com/a/6ZV16bV third: https://imgur.com/a/stRTh25 Link to binary used for this: https://www.python.org/ftp/python/3.8.0/python-3.8.0b3-amd64.exe -- components: Installation, Windows files: python_3.8b3_screen02_optional_features_2019-08-02_9-56-02.png messages: 348907 nosy: Christopher Brousseau, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: 3.8b3 - windows install gui/ inconsistent options type: behavior versions: Python 3.8 Added file: https://bugs.python.org/file48527/python_3.8b3_screen02_optional_features_2019-08-02_9-56-02.png ___ Python tracker <https://bugs.python.org/issue37745> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37745] 3.8b3 - windows install gui/ inconsistent options
Christopher Brousseau added the comment: Ah - I didn't realize the nuances here - thank you for clearing that up for me. Understand the design goal of keeping window size and using only checkboxes - simple. Also agree some text changes may help, here are some suggestions for your consideration: screen 1 - install python recommend we change "install launcher" to "install py launcher" to be explicit. Long term - it would be cleaner if the user had only 'default' and customize installation on this screen, with all configurations either bundled under Default, or moved to other screens for 'Customized' installs. We could add notes under default that we're installing python for all users, py launcher, adding Python to PATH, etc. If a user does not have admin privileges, it may not be helpful to them to present choices they can't install. For a default install - we could test if user has admin privileges and install for all users, or fall back to 'user' only install. screen 2 - optional features recommend we move "for all users" to screen 3, since this screen is about features to add, while the following screen is about how they are configured on the system. If this isn't possible in this release, consider 1. changing current "py launcher" checkbox to "upgrade py launcher" 2. moving "for all users" to next line down - looks like we have space 3. changing "for all users" to "py launcher for all users" screen 3 - advanced options two recommendations: 1. change "install for all users" to "install python for all users" 2. insert checkbox for "install py launcher for all users" as 2nd item in list. This would then be directly above the existing "Associate files with Python" checkbox -- ___ Python tracker <https://bugs.python.org/issue37745> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37745] 3.8b3 - windows install gui/ inconsistent options
Christopher Brousseau 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 <https://bugs.python.org/issue37745> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
