Installation and de-installation of Python 2.2.2 with WarpIN
============================================================

Installation
------------

Before installing this new release please de-install any old Python
versions. This avoids path conflicts. For more information on this,
see below ("Are you able to start the right Python version from the
command line?").

If your Python system doesn't work after the WarpIN installation,
consider these points:

- Have you rebooted your computer?
  
  The WarpIN installation modifies some environment settings in the
  config.sys, so rebooting is necessary.

  (I've read the WarpIN documentation and am aware of the cons of
  modifying the config.sys . If you want, you may use a startup
  script for Python similar to compileall.cmd .)
  
- Are you able to start the right Python version from the command
  line?
  
  You call Python from the command line via
  
  > python

  and this doesn't work or another as the expected version is
  started. If this happens, you may have another Python version
  installed, which still has related settings in the config.sys.

  The WarpIN installation script adds PATH and LIBPATH entries at the
  right of the corresponding setting. Thus, you may have something
  like

  PATH=...;e:\python222;...;h:\python;...

  In this case the interpreter probably can't be started, so
  remove the references to the old version.

  An alternative solution to this problem is outlined in the
  file README.os2emx.multiple_versions.

- Where's the WPS folder gone?

  Looking at it from a commandline, the folder "Python 2.2.2" seems
  to be empty. However, you shouldn't attempt to delete it because
  it actually contains the Workplace Shell objects that you see on
  the desktop after the WarpIN installation.

De-installation
---------------

If you have installed multiple packages, i. e. more packages than the
core distribution, WarpIN (version 0.9.20, and probably all older
versions) shows an error when you remove the packages at once.

This is due to the fact that the documentation and the examples
packages create objects in a WPS folder which is made on installation
of package 1. However, when de-installing, package 1 and the whole WPS
folder is removed so that the removal of the objects from the other
packages fail (because they were already deleted with the folder).

You have one of two choices:

- After you de-installed _all_ packages, highlight the packages marked
  with a red cross in WarpIN. Then select "Remove database entry" from
  the context menu. You may have to do this with one package at a
  time.

- Explicitly de-install the other packages than the core first, then
  the core package. So the WPS objects will be destroyed in the
  correct order.

Currently, WarpIN is not able to remove files it has not generated
itself. This regards the *.pyc files which are made during the
installation with a REXX/Python script. If you want to remove all
traces of Python after the WarpIN de-installation you can do this
safely with the WPS (given that you don't delete files that are
important for you :-) ).

Further sources of information
------------------------------

If you have further problems or comments on the WarpIN installation
of Python 2.2.2 or the example scripts in the WPS folder contact me
at sschwarzer@sschwarzer.net .

For questions regarding the OS/2 port in general - not specially the
WarpIN installation - contact Andrew McIntyre (see README.os2emx).

For questions regarding Python in general - not specially the
OS/2 port - contact the Python community (see README.Python-2.2.2).

Credits
-------

Guido van Rossum for inventing Python
Andrew McIntyre for porting Python to OS/2 and eCS
Salvador Parra Camacho for telling me how to install WPUrl objects

----------------------------------------------------------------------

Have fun :-)

Stefan Schwarzer <sschwarzer@sschwarzer.net>

