tkp...@hotmail.com wrote:
> I fixed the problem by creating a file call MyPath.pth that has only
> one line
> H:/Python
>
> and placing it in the C:\Python31\Lib\site-packages directory. So as a
> practical matter, my problem is solved. That said, I'm still puzzled
> by why Python 3.1 acts up when
I fixed the problem by creating a file call MyPath.pth that has only
one line
H:/Python
and placing it in the C:\Python31\Lib\site-packages directory. So as a
practical matter, my problem is solved. That said, I'm still puzzled
by why Python 3.1 acts up when I set the environment variable
PYTHONPA
I run Python under Windows XP SP3, and for the longest time, I have
installed it on my C: drive under C:\PythonXX (XX = 20, 21., 26),
and maintained all my Python files on our network in a directory
called H:\Python that I point to by creating an environment variable
called PYTHONPATH. I recent
