LilyPond's python clashes with default installation on Windows

[Florian Zeitz]

I have installed LilyPond on my Windows XP box and I have to say I like
it a lot, but I recently ran into the following problem:
Lilyponds Windows installer for some reason adds lilyponds bin directory
to the path. Beneath other things this contains a python.exe and a
python24.exe.
When I wanted to execute a certain python script from cmd, assuming I
was using the systems python interpreter of course, importing a module
failed, because it used lilyponds (local) python interpreter.
Obviously when a user has installed his own python he doesn't wants to
invoke lilyponds from cmd by default.