('win ' ( : aug : : more deleted 'if sys platform[: ='win'print('hello windows'hello windows if you have code that must act differently on different machinessimply test the sys platform string as done herealthough most of python is cross-platformnonportable tools are usually wrapped in if tests like the one here for instancewe'll see later that some program launch and low-level console interaction tools may vary per platform--simply test sys platform to pick the right tool for the machine on which your script is running the module search path the sys module also lets us inspect the module search path both interactively and within python program sys path is list of directory name strings representing the true search path in running python interpreter when module is importedpython scans this list from left to rightsearching for the module' file on each directory named in the list because of thatthis is the place to look to verify that your search path is really set as intended +the sys path list is simply initialized from your pythonpath setting--the content of any pth path files located in python' directories on your machine plus system defaults--when the interpreter is first started up in factif you inspect sys path interactivelyyou'll notice quite few directories that are not on your pythonpathsys path also includes an indicator for the script' home directory (an empty string-something 'll explain in more detail after we meet os getcwdand set of standard library directories that may vary per installationsys path [''' :\\pp thed\\examples'plus standard library paths deleted surprisinglysys path can actually be changed by programtoo script can use list operations such as appendextendinsertpopand removeas well as the del statement to configure the search path at runtime to include all the source directories to which it needs access python always uses the current sys path setting to importno matter what you've changed it tosys path append( ' :\mydir'sys path [''' :\\pp thed\\examples'more deleted ' :\\mydir'+it' not impossible that python sees pythonpath differently than you do syntax error in your system shell configuration files may botch the setting of pythonpatheven if it looks fine to you on windowsfor exampleif space appears around the of dos set command in your configuration file ( set name value)you may actually set name to an empty stringnot to valueintroducing the sys module