Environment

To get the most out of Wing, it is important to set these values in the Environment tab correctly for your project:

Python Executable -- When the Custom radio button is checked and the entered field is non-blank, this can be used to set the full path to the Python executable that should be used when debugging source code in this project. When Use default is selected, Wing tries to use the default Python obtained by typing python on the command line. If this fails, Wing will search for Python in /usr/local and /usr (on Linux/Unix) or in the registry (on Windows).

Python Path -- The PYTHONPATH is used by Python to locate modules that are imported at runtime with the import statement. When the Use default checkbox in this area is checked, the inherited PYTHONPATH environment variable is used for debug sessions. Otherwise, when Custom is selected, the specified PYTHONPATH is used.

Environment -- This is used to specify values that should be added, modified, or removed from the environment that is inherited by debug processes started from Wing IDE and is used to expand environment variable references used in other properties. Each entry is in var=value form and must be specified one per line in the provided entry area. An entry in the form var= (without a value) will remove the given variable so it is undefined. Note that you are operating on the environment inherited by the IDE when it started and not modifying an empty environment. When the Use system environment choice is set, any entered values are ignored and the inherited environment is used without changes.

Debug

The following properties are defined in the Debug tab:

Initial Directory -- When the Use default radio button is checked, the initial working directory set for each debug session will be the location where the main entry point file (if any) or project file is located. Otherwise, when Custom is selected, the specified directory is used or, when blank, the project file's directory is used.

Build Command -- This command will be executed before starting debug on any source in this project. This is useful to make sure that C/C++ extension modules are built, for example in conjunction with an external Makefile or distutils script, before execution is started. The build is configured through and takes place in the OS Commands tool.

Options

These project options are provided:

Project Type -- This can be used to select whether or not the project will be shared among several developers. When shared, the project will be written to two files, one of which can be shared with other developers. See Project Types for details.

Default Encoding sets the default text encoding to use for files when the encoding cannot be determined from the contents of the file. This applies to all files opened when the project is open, whether or not they are part of the project. By default, this falls back to the value set by the Default Encoding preference.

Preferred Line Ending and Line Ending Policy control whether or not the project prefers a particular line ending style (line feed, carriage return, or carriage return + line feed), and how to enforce that style, if at all. By default, projects do not enforce a line ending style but rather insert new lines to match any existing line endings in the file.

Preferred Indent Style and Indent Style Policy control whether or not the project prefers a particular type of indentation style for files (spaces only, tabs only, or mixed tabs and spaces), and how to enforce that style, if at all. By default, projects do not enforce an indent style but rather insert new lines to match any existing indentation in the file.

Extensions

The Extensions tab of Project Properties is used to control revision control and other add-ons on a per-project basis:

Enable Revision Control and Revision Control System are used to turn on a particular revision control integration for this project. Currently Subversion, CVS, and Perforce are supported.

Enable Zope2/Plone Support and Zope2 Instance Home are used for Zope 2.x and Plone projects to provide the Instance Home directory used by Zope. This is needed because Zope 2.x implements import magic that works differently from Python's default import and thus adding the instance home directory to PYTHONPATH is not sufficient. Wing's source analyzer needs this extra clue to properly find and process the Zope instance-specific sources.

When this option is activated, Wing will also offer to add the relevant Zope2/Plone files to the project, and to install the control panel for configuring and initiating debug in Zope2/Plone. See the Zope How-To for details.