Repository navigation
[doc] Missing items in installation/setup instructions #56645
Description
Activity
The Boston Python Workshop folks have some detailed step-by-step instructions on getting Python up and running ([1]).
Given that this can be a pain point for new users (primarily on Windows), it may be good to reference these instructions from the official docs. (Alternatively, we could use them as the basis for a "HOWTO" in the official docs and update release.py to adjust the relevant links. That's a lot more work than just adding a link, though)
[1] http://openhatch.org/wiki/Boston_Python_Workshop_3/Friday
I am not sure that is comprehensive enough. It is just organized into
OS specific sections and gives little details further on.
So, -1 to this, but +1 to the general idea of having detailed install
and get started documentation.Goal #1: set up Python
I believe http://docs.python.org/dev/using/ covers this.
Goal #2: prepare a text editor
This is missing from our docs. (My first thought was that it was out of scope, but for complete beginners, it would be nice to give a few pointers.)
Goal #3: practice starting and exiting Python
The tutorial has one page about that.
Goal #4: practice navigating the computer from a command prompt
Out of scope?
Goal #5: practice running Python code from a file
This is probably in the tutorial or using docs, I have to check.
Goal #6: get dependencies installed for the Saturday projects
This used to be non-standard, but now that we have packaging and pysetup, I translate this item to a doc bug: Explain how to use pysetup to get dependencies (in using, I think).
Nothing to add, IMO.
Nice, I didn't know we have those comprehensive using docs. However, they should be linked from http://docs.python.org/dev/tutorial/interpreter.html (definitely inline and perhaps a see also).
So what we're looking for is comprehensive HOWTOs for installing and running Python on Windows, OSX and Linux to be added to http://docs.python.org/howto/index.html?
IMO we don’t need HOWTOs that duplicate existing docs, but we may need additions to the existing tutorial and “using” docs. See http://bugs.python.org/issue12436#msg140141
I propose we close this, because it adds a little value as a separate bug. If there are specific sections in the docs that can be improved, we can deal with that.
I propose that we just narrow the scope of this report. If you agree with my earlier message, the current docs just need a few patches:
- How to prepare a text editor
- How to run Python code from a file (if the tutorial or using docs don’t already have it).
It would also be nice to have feedback from beginners about our tutorial and using docs: Are they comprehensive and easy to find?
- changed the title
[-]Provide reference to detailed installation instructions[/-][+]Missing items in installation/setup instructions[/+]on Aug 1, 2011 - How to prepare a text editor
See: http://docs.python.org/dev/using/unix.html#editors
- How to run Python code from a file (if the tutorial or using docs don’t already have it).
See: http://docs.python.org/dev/using/unix.html#miscellaneous
- How to prepare a text editor
Thanks Mike! So the first item is covered (at least for UNIX, can you check the Windows docs too?), but not the second. The item you linked to explains how to modify a script so that it’s possible to run ./script on Unix, but does not give an actual example of running it, nor does it explain “python script” or “python script.py” or “python -m module”.
Thanks Mike! So the first item is covered (at least for UNIX, can you
check the Windows docs too?), but not the second.http://docs.python.org/dev/using/windows.html Makes no reference to preparing a text editor. This I could help with but...
The item you linked
to explains how to modify a script so that it’s possible to run
./script on Unix, but does not give an actual example of running it,
nor does it explain “python script” or “python script.py” or “python -m
module”.Some one else would have to write this part unless you can give me some info about how it should be worded.
11 remaining items
Thanks, I will take all contributions and suggestions and propose one patch.
I am able to start working on this issue again, Eric. If you want to give me the status of your patch I can either help you finish it up or I can make one this week.
My computer currently doesn’t boot so I can’t check if I had started or not. You can propose a patch incorporating the various suggestions, or give me some days to read this again and make a summary of what I would have done. Thanks!
Here is a patch for just Notepad++.
Wrapped my text columns to 80. Ignore v2.
This issue is not newcomer friendly, I remove the easy keyword.
- added3.8 (EOL)end of lifeend of life3.9 (EOL)end of lifeend of life3.10 (EOL)end of lifeend of life
on Nov 6, 2020 - changed the title
[-]Missing items in installation/setup instructions[/-][+][doc] Missing items in installation/setup instructions[/+]on Nov 6, 2020 This issue is stale, is there any interest in pursuing it?
- addedpendingThe issue will be closed if no feedback is providedThe issue will be closed if no feedback is provided
on Sep 18, 2025
Metadata
Metadata
Assignees
Labels
Projects
- StatusShow more project fieldsTodo
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: