Why does Python never add itself to the Windows path?

[Gabriel Genellina]

At Saturday 30/12/2006 21:55, Ben Sizer wrote:

>python setup.py install
>
>On Unix, you'd run this command from a shell prompt; on Windows, you
>have to open a command prompt window (``DOS box'') and do it there; "
>
>Pretty much none of the instructions in that part of the docs will work
>without you altering your path beforehand. Python's cross-platform
>nature means people rightly expect the same instructions to work on
>Linux and Windows from a standard installation. Right now, they don't.

Notice that there is NO need to alter the system path. You just have 
to tell Windows where python.exe resides; there is a per-application 
path located at 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths.
In order to launch Python just writing "python" at the command 
prompt, the installer should -instead of playing with the system 
path- create a new key below App Paths, named "python.exe", and set 
its default value to the full path of the installed python executable.
See 
http://msdn.microsoft.com/library/en-us/shellcc/platform/shell/programmersguide/shell_basics/shell_basics_extending/fileassociations/fa_perceived_types.asp


-- 
Gabriel Genellina
Softlab SRL 


	

	
		
__________________________________________________ 
Preguntá. Respondé. Descubrí. 
Todo lo que querías saber, y lo que ni imaginabas, 
está en Yahoo! Respuestas (Beta). 
¡Probalo ya! 
http://www.yahoo.com.ar/respuestas