In analysing your source, Wing will use the Python interpreter and
PYTHONPATH that you have specified using Configure Python
in the Edit menu. Whenever any of these values changes, Wing
will re-analyze some or all of your source code.
When Wing tries to find analysis information for a particular module or
file, it takes the following steps:
- The path and same directory as the referencing module are searched for
an importable module
- If the module is Python code, Wing statically analyses the code to extract
information from it
- If the module is an extension module, Wing looks for a *.pi interface
description file as described later in this section
- If the module cannot be found, Wing tries to import it in a separate
process space in order to analyze its contents
- If a debug process is active, Wing tries to read relevant type information
from the live runtime state associated with the source code