<type>wingtip</type>
<domain>intro</domain>
<id>properties</id>
<title>Project and File Properties</title>
<date>$Date$</date>
<version>$Revision$</version>
<product>all</product>

Be sure to configure the ``Python Executable`` in your `Project Properties
<script:view_project_properties>`__ so that Wing knows what version of Python you are
using. You may also need to add to ``Python Path`` if your code modifies ``sys.path`` at
runtime to include directories outside of the Python installation.

This information is used by the debugger when executing your code and by
`auto-completion <ref:edit/auto-completion>`__, `goto-definition <ref:edit/navigating-source>`__,
~~~if WINGPER or WINGPRO:
`Source Assistant <ref:edit/source-assistant>`__, `Source Browser <ref:browser/index>`__,
~~~
~~~if WINGPRO:
`Find Uses <ref:edit/points-of-use>`__, `Refactoring <ref:refactoring/index>`__, 
~~~
and other tools.

Command line arguments to use for debugging may be set with ``Current File Properties`` in
the ``Source`` menu, or by right clicking on an editor and selecting ``Properties``. This
also provides the ability to override Python environment settings for that specific file.

See `Project Projects <ref:proj/project-properties>`__ and `File Properties
<ref:proj/file-properties>`__ for details.
