| Item | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Name | In this text box, specify the name of the current run/debug configuration. | ||||||||
| Update your script | This section contains vital information required to prepare for remote debugging.
| ||||||||
| Local host name | Specify the name of the local host, by which the IDE is accessible from the remote host. This host name will be automatically substituted to the command line. By default, localhost is used. | ||||||||
| Port | Specify the port number, which will be automatically substituted to the command line. If the default post number (0) is used, then PyCharm substitutes an arbitrary number to the command line at each launch of this debug configuration; if you specify any other value, it will be used permanently. | ||||||||
| Path mappings | Use this field to create mappings between the local and remote paths. Clicking the browse button 
results in opening Edit Path Mappings dialog box, where you can add new path mappings, and delete the selected ones.
| ||||||||
| Redirect output to console | If this check box is selected, the output and error streams will be redirected to the PyCharm console, and the command line is complemented with the stdoutToServer=True, stderrToServer=True | ||||||||
| Suspend after connect | If this check box is selected, the debugger will suspend immediately after connecting to the IDE, on the next line after the settrace call. If this check box is not selected, the debugger will only suspend upon hitting a breakpoint, or clicking  , and the command
line is complemented with suspend=False
|
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 | In this area, specify the actions to be performed prior to executing the current run/debug configuration.
|
