<type>documentation</type>
<domain>edit</domain>
<id>analysis-helping-env</id>
<title>Setting the Correct Python Environment</title>
<date>$Date: 2007-02-09 12:04:39 -0500 (Fri, 09 Feb 2007) $</date>
<version>$Revision: 14785 $</version>
<product>all</product>

The most common reason that Wing fails to provide useful source code analysis is failure
to configure ``Python Executable`` and ``Python Path`` in `Project Properties
<ref:proj/project-properties>`__. This is important so that Wing knows which version
of Python your code is designed for, and so it can find any modules that are not on
Python's default ``sys.path``.

In cases where code makes changes to ``sys.path`` at runtime, it may help to set the file
where those changes are made as the `main entry point
<ref:debug/main-entry-point>`__. Wing tries to read ``sys.path`` changes and
incorporate them into the Python environment used for source code analysis. If this fails,
add the appropriate items to `Python Path
<script:view_project_properties#highlighted_attrib="proj.pypath">`__ in ``Project
Properties``.
