executablesand changing just py_python as needed conclusionsa net win for windows to be fairsome of the prior section' pitfalls may be an inevitable consequence of trying to simultaneously support unix feature on windows and multiple installed versions in exchangeit provides coherent way to manage mixed-version scripts and installations you'll probably find the windows launcher shipped with and later to be major asset once you start using itand get past any initial incompatibilities you may encounter in factyou may also want to start getting into the habit of coding compatible unixstyle #lines in your windows scriptswith explicit version numbers ( #!/usr/binpython not only does this declare your code' requirements and arrange for its proper execution on windowsit will also subvert the launcher' defaultsand may also make your script usable as unix executable in the future but you should be aware that the launcher may break some formerly valid scripts having #linesmay choose default version that you don' expect and your scripts can' useand may require configuration and code changes on the order of those it was intended to obviate the new boss is better than the old bossbut seems to have gone to the same school for more on windows usagesee appendix for installation and configuration for general conceptsand platform-specific documents in python' manuals set appendix bthe python windows launcher