19. Changes for ActivePython

The following changes were made to this document in order to ship it with ActivePython:

27a28,29
> The version you are reading has been modified by Paul Prescod to fit the ActivePython context better.
> 
45d46
< 
46a48,52
> 
> The version you are reading has been modified to better fit the
> ActivePython context. For instance descriptions of PythonWin have been
> added. Comments about the PythonWin and ActivePython references in the
> document can be sent to \url{http://activepythonbugs.activestate.com}.
57c63
< <li><a href="http://www.python.org/doc/">python Documentation</a>}
---
> <li><a href="http://www.python.org/doc/">python Documentation</a>
90,91d95
< Now, on to more important things.  In order to program in Python you need the Python software.  If you don't already have the Python software go to http://www.python.org/download/ and get the proper version for your platform.  Download it, read the instructions and get it installed.  
< 
93c97,98
< First you need to download the appropriate file for your computer from \url{http://www.python.org/download}.  Go to the 2.0 link (or newer) and then get the windows installer if you use Windows or the rpm or source if you use Unix.  
---
> This tutorial presumes you have already installed ActivePython. If you
> have not, go to: \url{http://aspn.activestate.com/ASPN/Downloads/ActivePython}|
97c102,106
< If you get the Unix source make sure you compile in the tk extension if you want to use IDLE.
---
> If you get the Unix source make sure you compile in the tk extension
> if you want to use IDLE.
> 
> Whether you are building from source or not, Unix users need to
> install Tcl/Tk itself.
100c109,113
< Go into IDLE (also called the Python GUI).  You should see a window that has some text like this:
---
> If you are on Windows, go into PythonWin.
> 
> If you are in Unix run IDLE.pyw.  
> 
> You should see a window that has some text like this:
102,106c115,118
< Python 2.0 (#4, Dec 12 2000, 19:19:57) 
< [GCC 2.95.2 20000220 (Debian GNU/Linux)] on linux2
< Type "copyright", "credits" or "license" for more information.
< IDLE 0.6 -- press F1 for help
< >>> 
---
> PythonWin 2.1 (#15, Apr 18 2001, 14:10:26) [MSC 32 bit (Intel)] on win32.
> Portions Copyright 1994-2001 Mark Hammond (MarkH@ActiveState.com) -
> see 'Help/About PythonWin' for further copyright information.
> >>>
113c125
< Go into IDLE if you are not already.  Go to \verb'File' then \verb'New Window'.  In this window type the following:
---
> Go into PythonWin (on Windows) or IDLE (on Unix) if you have not already.  Go to \verb'File' then \verb'New Window'.  In this window type the following:
120c132,135
< Next run the program by going to \verb'Edit' then \verb'Run script'.  This will output \verb'Hello, World!' on the \verb'*Python Shell*' window.  
---
> Next run the program. In PythonWin, you can do this by going to \verb'File' and then \verb'Run'.
> In IDLE, you would use \verb'Edit' then \verb'Run script'.  This will
> output \verb'Hello, World!' on the \verb 'Interactive
> Window'(PythonWin) or \verb'*Python Shell*' window (IDLE).  
142c157
< Otherwise go into IDLE, create a new window, and create it as in section \ref{create}.
---
> Otherwise go into PythonWin or IDLE, create a new window, and create it as in section \ref{create}.
1031a1047,1070
> \section{Debugging tools}
> Debugging can be such a pain that there are tools designed to help you
> find the bugs in your programs called "debuggers." This tutorial will
> not go into detail on debuggers but it is useful to know that they
> exist. That way, you can investigate them on your own.
> 
> Python comes with a built-in "command line" debugger called
> PDB. It is documented in the Python manual. PDB is considered a little
> primitive by those who are used to debuggers with more advanced user
> interfaces. PythonWin and IDLE both have debuggers that are 
> easier to use than PDB.
> 
> There are various commercial debuggers for Python which are more
> advanced than PythonWin and IDLE. They are typically better at 
> helping you to see the values of your variables. PythonWin and IDLE
> are also not very good at debugging graphical applications. If your
> program has a severe bug, it can even crash PythonWin or IDLE. 
> Most commercial IDEs do not have these flaws. Some commercial IDEs
> also allow debugging of programs running on remote machines or 
> embedded in applications.
> 
> ActivePython users are encouraged to try Komodo if PythonWin or IDLE
> do not meet your needs: \url{http://www.activestate.com/Komdo}
> 
2682a2722,2727
> 
> \chapter{Changes for ActivePython}
> 
> \begin{verbatim}
>