PythonPath not working with 2.2.3 on Win ME

[Rami A. Kishek]

Answering my own question for the benefit of others upgrading from
1.5.2, after a painstaking search on sourceforge.net, I found a cryptic
exchange between the developers which gave me a clue.   In the registry,
you need to add your own user directories that you want to be in the
PythonPath into the SUB-Keys of Python (i.e. Pythonwin or Win32) rather
than the main Key, which doesn't get read.  It was not clear from what I
found whether this feature is deliberate or whether it is a bug, and it
is not clear whether my workaround is the elegant solution, but it
worked.   

It would be nice, though, if the developers included one line about that
issue in the installation notes for the clueless!

"Rami A. Kishek" wrote:

> I just upgraded my Python on WinME machine from Python 1.5.2 to 2.2.3
> (in a separate directory).  Using the Pythowin Pythonpath browser, I
> edited the python path to add my scripts directories.  Then I tried to
> import my scripts and they're not visible.  I tried many things:

...
 
> Each and every time however, when I start python, import sys, then check
> sys.path, the path I get does not reflect the changes I made, and of
> course, as a result my own scripts don't work (they try to import each
> other).  ...  The really strange thing is: the
> pythonpath in the Pythonwin Browser and the registry (which are the
> same) have really nothing to do with the path I get by checking
> sys.path!  Not even the built-in directories are the same.