[Tutor] A few Python Mysteries

[Alan Gauld]

On 21/12/11 19:56, Wayne Watson wrote:

>> To clarify: Python on Windows does **not** put itself on the System
>> PATH when installed.
> So, PythonNN, where NN is the version, should never appear in PATH?

Not from a standard Python installation.
But other programs whjich use Pythonn may install a version and modify 
the PATH for you, or you may, for your own benefit, add it manually.
I always add a new Python version to my PATH as a matter of course.

> It's conceivable when I raised some of the questions a month of so ago,
> someone suggested putting PythonNN on the path.

Very possible indeed.

>> likely the application that *did* put it there is the **same**
>> application that is now complaining about the fact that it can't find
>> the Python 2.5 DLL when you boot up...
> See my mis-copy 26.dll in my other post to you.

OK, But the principle remains. If you have an app in your startup 
sequence that expects to find Python it will complain.

You can check your startup sequence using a Microsoft tool.
MSCONFIG or somesuch. Google Windows startup tool or similar...
You can disable individual programs and restart to find out
what is causing it.

>>> I have no idea why some remnant of why Python6 is hanging around. I
>>> uninstalled it long ago too.

The problem is that it is not hanging around and some app expects
it to be there. The error message is about a missing file...

One thing that may be significant...
Are you installing your Windows Python versions from
python.org or from ActiveState? They are very similar
but not identical.

-- 
Alan G
Author of the Learn to Program web site
http://www.alan-g.me.uk/