Configuration
| Item | Description |
|---|---|
| Project | Click this drop-down list to select one of the projects, opened in the same PyCharm window, where this run/debug configuration should be used. |
| Environment variable | This field shows the list of environment variables.
If the list contains several variables, they are delimited with semicolons. To fill in the list, click the browse button, or press Shift+EnterShift+Enter and specify the desired set of environment variables in the Environment Variables dialog box. To create a new variable, click  , and type the desired name and value.
By default, the variable PYTHONUNBUFFERED is set to 1. |
| Python Interpreter | Select one of the pre-configured Python interpreters from the drop-down list. |
| Interpreter options | In this field, specify the string to be passed to the interpreter. If necessary,
click  , and type the string in the editor. |
| Working directory | Specify a directory to be used by the running task.
Note
|
| 2.7.2+Add content roots to PYTHONPATH | Select this check box to add all content roots of your project to the environment variable PYTHONPATH; |
| Add source roots to PYTHONPATH | Select this check box to add all source roots of your project to the environment variable PYTHONPATH; |
| Host | In this text box, specify the host name to be used. |
| Port | In this text box, specify the port number where the server will start. |
| Additional options | In this text box, specify the options of the django-admin.py utility. Refer to
the django-admin.py and manage.py
documentation for details. |
| Run browser | Select this check box to start the Django server in the default browser. In the text field below, enter the IP address where the Django server will start. |
| Test server | If this check box is selected, a Django development server is launched with the test database. If this check box is not selected, the development server will be used. |
| No reload | 2.0+If this check box is selected, the -- noreload option of the runserver
command becomes enabled. If this check box is not selected, PyCharm will not select it automatically, which means that debugging in autoreload mode is possible.
Refer to the option description This field is only available when the Test server check box is cleared. |
| Custom run command | Specify here the custom command you want to register with manage.py utility.
Such command, being properly added to your project, becomes available via the
Run manage.py task command on the menu. Refer to the section Writing custom django-admin commands for details.
|
Toolbar
| Item | Shortcut | Description |
|---|---|---|
|
| InsertInsert | Click this button to add new configuration to the list. |
| DeleteDelete | Click this button to remove the selected configuration from the list. |
| Ctrl+DCtrl+D | Click this button to create a copy of the selected configuration. |
| Edit defaults | Click this button to edit the default configuration templates. The defaults are used for the newly created configurations. |
 or 
| Alt+UpAlt+Up or Alt+DownAlt+Down | Use these buttons to move the selected configuration or group of configurations (folder) up and down in the list.
The order of configurations or folders in the list defines the order, in which configurations appear in the Run/Debug drop-down list on the main toolbar. |
 | Use this button to create a new folder.
If one or more run/debug configurations have the focus, then the selected run/debug configurations 0 are automatically moved to the newly created folder. If only a category has the focus, then an empty folder is created. |
Common options
| Item | Description | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Name | In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations. | |||||||||||||||||||||
| Defaults | This node in the left-hand pane of the dialog box contains the default run/debug configuration settings. Select the desired configuration to change its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations. | |||||||||||||||||||||
| Temporary configurations limit | Specify here the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list. | |||||||||||||||||||||
| Share |
Select this check box to make the run/debug configuration available to other team members.
The shared run/debug configurations are kept in separate xml files under .idea\runConfigurations folder, while the local run/debug configurations are kept in the .idea\workspace.xml. This check box is not available when editing the run/debug configuration defaults. | |||||||||||||||||||||
| Single instance only | If this check box is selected, this run/debug configuration cannot be launched more than once.
Every time a new run/debug configuration is launched, PyCharm checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place. This make sense, when usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources. If this check box is not selected, it is possible to launch as many instances of the runner as required. So doing, each runner will start in its own tab of the Run tool window. | |||||||||||||||||||||
| Before launch | Specify which tasks should be carried out before starting the run/debug configuration.
The specified tasks are performed in the order that they appear in the list.
|
