Whenever your Python source depends on PYTHONPATH (either set externally or by altering sys.path internally), you will also need to tell Wing about your path.
This value can be entered from the Project Properties dialog, which is accessible from the Project menu and the toolbar:
For this tutorial, you will at least need a PYTHONPATH that includes the subdir sub-directory of your tutorials directory as shown in the figure above. This contains a module used as part of the first coding example.
Note that in the screen shot above the PYTHONPATH has been set with the full path to the directory subdir. This is strongly recommended because it avoids potential problems finding source code when the starting directory is ambiguous, both for source code analysis purposes and in Wing's debugger. A partial path can be specified, but Wing will issue a warning explaining why this is a bad idea.
The configuration is used here for illustration purposes. You could easily run the example code without a PYTHONPATH by moving the path_example.py file to the same location as the example scripts, or by placing it into your Python installation's site-packages directory. Either of these allows Python to find the modules without altered PYTHONPATH.
|« 1.3. Tutorial: Set Up a Project||Table of Contents||1.5. Tutorial: Introduction to the Editor »|