help! - cmd line interpreter gone "dumb"

Tim tim.harford at rogers.com
Sun Jul 6 19:59:17 EDT 2003


Yes, reboot or have the programmer give his head a shake. ;-)

I love this language, but getting used to the little set up details I
guess...Half of it was my own ignorance, but it's not obvious.

For the record...

if I don't define any paths for Python, it naturally knows were to go for
the core + libraries.
but, if you define the PYTHONPATH in the environment--only those directories
are searched. It was probably the late night that had me forget when I
changed things (funny--its seemed to work for a long while, but the changes
may not have been reflected if I had the same command window open the entire
evening (this was the case, I think).

It makes sense...

Tim



"Gerhard Häring" <gh at ghaering.de> wrote in message
news:mailman.1057524309.16869.python-list at python.org...
> Tim wrote:
> > Maybe I've been working too long, but has anyon had their python
interpreter
> > stop taking commands.
> >
> > The IDLE version works fine, but under Windoze:
> >
> > 1) execute "python" in teh command shell
> > 2) ...interpreter comes up fine
> > 3) type in anything and you get "SyntaxError: invalid syntax"
> >
> > Literally, you could type in "import sys" or anything common and you get
the
> > same results.
>
> I've seen that when I used os.spawn* (or was it os.execv*?), apparently
> in a wrong way.
>
> > Any help greatly appreciated--thanks.
>
> Typical Windows answer: reboot and try again ;-)
>
> -- Gerhard
>






More information about the Python-list mailing list