homepage

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).
> Goal #7: start learning Python!
> Goal #8: Checkoff
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?

> - 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 

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.

> http://docs.python.org/dev/using/windows.html Makes no reference to
> preparing a text editor. This I could help with but...
Cool, please follow the guidelines in the devguide to make a patch for 3.2. It should be something short, like the unix docs, mostly to recommend Notepad++ I think.
For Windows users, added a section about how to use a terminal and possibly a link to PowerShell would be another good addition IMO.
> Some one else would have to write this part unless you can give me
> some info about how it should be worded.
I’ll propose a patch.

> mostly to recommend Notepad++ I think.
In addition to Notepad++ do you think it would be a good idea to at least mention Vim and Emacs with a disclaimer about the learning curve?
> For Windows users, added a section about how to use a terminal and 
Do you think it would be a good idea to add instructions on how to add Python to the Path in Windows? It could be 'borrowed' from the Boston Python Workshop Page I would think. It's pretty long but useful considering how much trouble I have had having to do this myself under Windows.

> In addition to Notepad++ do you think it would be a good idea to at
> least mention Vim and Emacs with a disclaimer about the learning curve?
I'm not sure how many windows user use Vim/Emacs. Maybe PyScripter could be mentioned too, but I'm not sure how popular it is and if there are better alternatives.
> Do you think it would be a good idea to add instructions on how to add
> Python to the Path in Windows? 
Yes, but isn't there a script somewhere that does that already?

> In addition to Notepad++ do you think it would be a good idea to at
> least mention Vim and Emacs with a disclaimer about the learning curve?
I'm a bit surprised. I would think the devguide is aimed are people who are *already* programmers, and have chosen their tools. Therefore I don't know how such material is useful, and the devguide is already hefty enough.

Oops. I just noticed this issue is not talking about the devguide, but the general docs. Please ignore the message above.

> In addition to Notepad++ do you think it would be a good idea to at
> least mention Vim and Emacs with a disclaimer about the learning
> curve?
No. If someone is looking at this page and doesn’t already have a text editor they’re familiar with, I think Notepad++ is the right tool to suggest.
> Do you think it would be a good idea to add instructions on how to add Python
> to the Path in Windows?
The doc already has that somewhere, unless I misremember.
> Yes, but isn't there a script somewhere that does that already?
One or more in Tools/scripts and maybe in PC or PCbuild too.

Here is what I have so far:
> For Windows users, added a section about how to use a terminal
How to use a terminal
Open a command prompt:
* On Windows Vista or Windows 7: click on the Start menu (the Windows logo in the lower left of the screen), type cmd into the Search field directly above the Start menu button, and click on "cmd" in the search results above the Search field.
* On Windows XP: click on the Start menu (the Windows logo in the lower left of the screen), click on "Run...", type cmd into the text box, and hit enter.
Commands used in terminal
* cd C:\ - Puts you in the root directory of the C drive.
* cd Python32 - Puts you in the directory where Python 3.2 is installed.
* dir - This command lists the contents of the Python32 directory.
* python - This command will invoke python.exe and bring up the interpreter.
> a link to PowerShell 
Windows PowerShell
Windows PowerShell is a task-based command-line shell and scripting language designed for system administration. It can be obtained here: http://technet.microsoft.com/en-us/library/bb978526.aspx.

> Open a command prompt:
Another alternative is win+r -> type 'cmd' -> hit enter. This should work on all the Windows versions.
> * cd C:\ - Puts you in the root directory of the C drive.
> * cd Python32 - Puts you in the directory where Python 3.2 is installed.
What if it's not installed there? Maybe it's better to say something like "use the 'cd' command to move to the directory where Python is installed" possibly mentioning the default installation directory and 'cd ..'.
> * dir - This command lists the contents of the Python32 directory.
> * python - This command will invoke python.exe and bring up the 
interpreter.
If the dir is already added to the PATH 'python' will work already without having to navigate to the installation dir.
Also if the user installed Python there should be a "Python (command line)" entry in the start menu that brings up the interpreter.

Thanks, I will take all contributions and suggestions and propose one patch.

>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.