[Tutor] Tutor Digest, Vol 45, Issue 30

Tony Cappellini cappy2112 at gmail.com
Mon Nov 12 05:45:17 CET 2007

> Message: 4
> Date: Mon, 12 Nov 2007 00:16:35 -0000
> From: "Alan Gauld" <alan.gauld at btinternet.com>
> Subject: Re: [Tutor] Wrong version of Python being executed
> To: tutor at python.org
> Message-ID: <fh861b$up1$1 at ger.gmane.org>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
>         reply-type=original

> This is very important. If you just type python at the Run
> dialog it uses a different algorithm to find the exe than if
> you type python at a DOS prompt inside a CMD window.

I never type anything in the Run dialog other than Regedit, or CMD.
I dont want that to sound defensive, but usually when I need a CMD
prompt, I'm need to be there for a long time, and that's why I open
It never even occurred to me to type Python at the Run prompt.

Most of the time, I open a cmd prompt IN the directory where I want to
run a script, by using "Command Prompt Here", from Microsoft.
(why isn't this built into the OS after all this time ??????????)

But while troubleshooting this problem, I've not been using it, and
have been CD'ing down to where my sources are.

> Its the second algorithm that is used if you type
> python foo.py at a cmd prompt but the first that
> is used if you double click foo.py within explorer
I typically dont double click my scripts, unless they are guis, or exes'

> That *shouldn't* make any difference...but you can never be 100% sure!

I think a this point, I'll just re-install 2.3 and 2.5 to see if that
fixes it, with a reboot in-between.
I dont know what else to do.

More information about the Tutor mailing list