with an execfile('texteditor py'call the pyw suffix avoids the dos console streams window pop up when launched by clicking on windows todaypyw files can be both imported and runlike normal py files (they can also be double-clickedand launched by python tools such as os system and os startfile)so we don' really need separate file to support both import and console-less run modes retained the pythoughin order to see printed text during development and to use pyedit as simple ide--when the run code option is selectedin nonfile modeprinted output from code being edited shows up in pyedit' dos console window in windows clients will normally import the py file user configurations file on to the code firstpyedit' user configuration module is listed in example - this is mostly conveniencefor providing an initial look-and-feel other than the default pyedit is coded to work even if this module is missing or contains syntax errors this file is primarily intended for when pyedit is the top-level script run (in which case the file is imported from the current directory)but you can also define your own version of this file elsewhere on your module import search path to customize pyedit see texteditor py ahead for more on how this module' settings are loaded its contents are loaded by two different imports--one import for cosmetic settings assumes this module itself (not its packageis on the module search path and skips it if not foundand the other import for unicode settings always locates this file regardless of launch modes here' what this division of configuration labor means for clientsbecause the first import for cosmetic settings is relative to the module search pathnot to the main file' packagea new textconfig py can be defined in each client application' home directory to customize pyedit windows per client converselyunicode settings here are always loaded from this file using package relative imports if neededbecause they are more critical and unlikely to vary the package relative import used for this is equivalent to full package import from the pp rootbut not dependent upon directory structure like much of the heuristic unicode interface described earlierthis import model is somewhat preliminaryand may require revision if actual usage patterns warrant example - pp \gui\texteditor\textconfig py ""pyedit (texteditor pyuser startup configuration module""#general configurations comment-out any setting in this section to accept tk or program defaultscan also change font/colors from gui menusand resize window when openimported via search pathcan define per client appskipped if not on the path complete gui programs