Re: STDWIN example

Josef Dalcolmo (josefd@ssl.Berkeley.Edu)
Wed, 14 Sep 1994 13:10:02 -0700 (PDT)

>
> > import stdwin
> > from stdwinevents import *
> >
> > ...
> >
> > at the second line the program exits ``module stdwinevents not found''.
> >
> > I didn't find it either.
>
> It's in the 'stdwin' subdirectory of the Lib directory. (Surprise!)
> To add this directory permanently to your module search path, you have
> to uncomment a line beginning with #STDWINPATH= in the Modules/Setup
> file.
>
> BTW this is my mistake -- the line for STDWINPATH in the Setup file is
> far away from the other lines for STDWIN. Will be corrected in 1.1.
>
> --Guido van Rossum, CWI, Amsterdam <Guido.van.Rossum@cwi.nl>
> <URL:http://www.cwi.nl/cwi/people/Guido.van.Rossum.html>
>

Well, I had already done all of the above, but it still didn't work. The
reason was that I did not run ``make install'' and ``make libinstall''.
Instead I left the tree in place after ``make'' and ``make test''.
``make test'' initializes PYTHONPATH properly for it's own purposes, but
when simply running python sys.path is initialized to something like
~/lib/python ... instead of ~/python-1.0.3/Lib ... since prefix is set for
the installation tree.

One solution is to set the environment variable PYTHONPATH to
~/python-1.0.3/Lib: ...

It would be nice, though for beginners like me if we wouldn't have to worry
about this path, e.g. the compiled in path should point to the ``right''
places where the original source tree is, unless one actually runs ``make
install''.

Hower, many thanks. Your comments helped me to get started in the right
direction. If I only new how to install stdwin on my linux box at home...
(I'll get the new 0.9.9 before I bug anybody, I have still 0.9.8)

- Josef