New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better identify Windows installer as installer only, not runner #85120
Comments
Some beginners on Windows think that python-3.8.3-amd64.exe, for instance, is for running python-3.8.3, leading to repeated and now tiresome questions on python-list and probably elsewhere. The latest example is "repair modify uninstall" with the core complaint that "after downloading and trying to launch it keeps saying repair modify uninstall". (Actually, 'modify' comes first.) In response, Grant Edwards suggested adding run instructions to the initial screen and asked a "Is the file name not clear that it's an installer?" For the naive, the answer, as is traditional, is 'no'. How about adding 'setup' or 'install', as I have seen occasionally. The initial screen is different according to whether an installed binary is absent or present. For the latter, add something like Python 3.8.3 {n} bit is installed for {who}. An optional add-on would be a button to open the doc page on using python on Windows. (I an not suggesting a button to actually run python.exe from the installer. Users should really learn how to start it properly according to platform and python-specific conventions and their particular needs.) Does the final screen after installation say anything about running the new install? (I cannot remember.) Ned: I don't think that this issue afficts Mac newbies. Perhaps python-xyz.pkg is more clearly not for running. But something you might watch for. |
The current "using" doc page is way too in-depth, but I'm actually okay with the idea of having a "Did you mean to launch Python? Press 'Start' and type 'Python' to find it" message on the Modify page of the installer. Perhaps the people hitting this problem would read the final page of the installer, but I suspect they're just like everyone else and don't read instructions until just-in-time. So if they're reaching the Modify page, that's the place to put them. |
Simple is fine. How about If you want to run Python, press Start and find 'Python 3.x' under 'P', or enter 'python' in the "Search for anything" box on the taskbar. If you don't have the time right now, where should this go? |
"on python-list and probably elsewhere"... I can confirm these questions get mailed to webmaster@python.org :) A couple of comments since I see these fairly frequently: The "using" doc page may have too much information for beginner tastes, but at least it answers a lot of questions. but it's hard to find... it would be nice if the OS-specific installation page actually pointed to it - or to a more concise alternative if that's preferred. Applies to Mac as well, as most people who install on Mac seem to have some surprise with it not launching the way they expect. Proposed text: "If you want to run Python, press Start and find 'Python 3.x' under 'P', or enter 'python' in the "Search for anything" box on the taskbar." - why not mention the Python Launcher here? Isn't that the preferred approach now for the pydotorg installer? |
Mats, thank you for chiming in. py.exe is preferred *if* one starts python from a command line. Some beginners have never seen one or know what it is. This is most likely to be true of people who don't know 'installer' from 'launcher'. The installer is usually launched from a browswer or possibly Explorer, not a console. That said, I would not mind also linking to whatever page, but I agree now with Steve about starting with something minimal that works, at least if the default 'install icons' was left checked. |
I'm not a habitual Windows user (a certain project is making me spend way more time there than usual), but if I start typing python to a Windows search, after the first two letters the launcher is usually the highlighted match ("Best match" it says on Win10), so it's not *just* from the command line. |
Assuming it fits, I'm going to update the 3.9+ post-install message to this (assume the HTML renders normally). Any comments? New to Python? Start with the <a href="https://docs.python.org/[ShortVersion]/tutorial/index.html">online tutorial</a> and <a href="https://docs.python.org/[ShortVersion]/index.html">documentation</a>. At your terminal, type "py" to launch Python, or search for Python in your Start menu. See <a href="https://docs.python.org/[ShortVersion]/whatsnew/[ShortVersion].html">what's new</a> in this release. Special thanks to Mark Hammond, without whose years of freely shared Windows expertise, Python for Windows would still be Python for DOS. |
Added a screenshot, after tweaking the spacing just a little. |
I still think there ought to be some pointer to https://docs.python.org/3/using/windows.html in there. |
I changed the middle paragraph to this: See <a href="https://docs.python.org/[ShortVersion]/whatsnew/[ShortVersion].html">what's new</a> in this release, or find more info about <a href="https://docs.python.org/[ShortVersion]/using/windows.html">using Python on Windows</a>. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: