PYTHONPATH & Win 98 - seems broken
piet at cs.uu.nl
piet at cs.uu.nl
Tue Sep 5 11:41:45 EDT 2000
>>>>> Steve Holden <sholden at holdenweb.com> (SH) writes:
SH> The sad fact appears to be that the interpreter does not use the
SH> PYTHONPATH variable when looking for the file named on the command
SH> line, only for modules referred to by "from" and "import" statements.
SH> In the UNIX environment you can just make your python script executable,
SH> then you can use the script name as long as it's in a directory on your
SH> PATH.
SH> You can do a similar thing in Windows NT (and, I believe, W2K, but I am
SH> not yet fighting that particular OS). This involves setting registry
SH> values to associate the ".py" extension with the interpreter.
SH> Windows 95 and 98 lose here, as there doesn't appear to be a way to
SH> associate arbitrary filename extensions with particular interpreters.
See PythonLauncher, http://www.toolwood.dk/freeware/PythonLauncher/
--
Piet van Oostrum <piet at cs.uu.nl>
URL: http://www.cs.uu.nl/~piet [PGP]
Private email: P.van.Oostrum at hccnet.nl
More information about the Python-list
mailing list