Run/debug configurations
PyCharm uses run/debug configurations to run, debug, and test your code. Each configuration is a named set of startup properties that define what to execute and what parameters and environment should be used.
With different startup properties, you can define different ways that PyCharm uses to execute your script. For example, you can execute the same code with different Python interpreters, providing various sets of environment variables, and getting input values from alternative files.
There are two types of run/debug configurations:
Temporary — created every time you run or debug functions or tests.
Permanent — created explicitly from a template or by saving a temporary configuration. Permanent configurations remain as part of your project until you remove them.
So whenever you run/debug or test your code, PyCharm either uses an existing permanent run/debug configuration or creates a new temporary one.
Permanent configurations have opaque icons while the icons of temporary configurations are semi-transparent.
The maximum number of temporary configurations is 5. The older ones are automatically deleted when new ones are added. If necessary, you can increase this limit in
.Create permanent run/debug configurations
PyCharm provides the following ways to create a permanent run/debug configuration:
Create from a template or copy an existing configuration.
Save a temporary configuration as permanent
Select a temporary configuration in the run/debug configuration switcher and then click Save Configuration.
Once you save a temporary configuration, it becomes permanent and it is recorded in a separate XML file in the <project directory>/.idea/ directory. For example, MyProject/.idea/Car.xml.
Alternatively, select a temporary configuration in the Run/debug configurations dialog and click on the toolbar.
PyCharm provides run/debug configuration templates for different languages, tools, and frameworks. The list of available templates varies depending on the installed and enabled plugins.
Create a run/debug configuration from a template
From the main menu, select
. Alternatively, press Alt+Shift+F10, then 0.In the Run/Debug Configuration dialog, click on the toolbar or press Alt+Insert. The list shows the run/debug configuration templates.
Select the desired template. If you are not sure which template to choose, refer to Run/debug configurations dialog for more information on particular templates.
Specify the run/debug configuration name in the Name field. This name will be shown in the list of the available run/debug configurations.
Select Allow parallel run if you want to allow multiple instances of the configuration to run at the same time. If this option is disabled, attempting to re-run the configuration will terminate the active session.
Set the run/debug configuration parameters.
In the Before launch section, define whether you want to perform any specific actions before launching the application, for example, execute some tools or scripts prior to launching the run/debug configuration.
For information on particular Before launch activities, refer to Before launch
Apply the changes and close the dialog.
Share run/debug configurations
If you are working in a team, you might want to share your run/debug configurations so that your teammates could run the application using the same configuration or enable them to remotely attach to the process you are running.
For these purposes, PyCharm provides a mechanism to store your run/debug configurations as project files and share them through VCS. The same mechanism can also be used when you want to send your configuration as a file to someone else. This saves a lot of time as run/debug configurations sometimes get sophisticated, and keeping them in sync manually would be tedious and error-prone.
From the main menu, select
. Alternatively, press Alt+Shift+F10, then 0.Select the run/debug configuration you want to share, enable the Store as project file option, and specify the location where the configuration file will be stored.
If compatibility with PyCharm 2019.3 and earlier is required, store the file in the default location.
(Optional) If the .idea directory is added to VCS ignored files, the .idea/runConfigurations subfolder will be ignored, too. If you use Git for your project, you can share .idea/runConfigurations only and leave .idea ignored by modifying .gitignore as follows:
/.idea/* !/.idea/runConfigurations
Run/debug configuration templates
All run/debug configurations are based on templates, which implement the startup logic, define the list of parameters and their default values. The list of available templates is predefined in the installation and can only be extended via plugins. However, you can edit default parameter values in each template to streamline the setup of new run/debug configurations.
Configure the default values for a template
From the main menu, select
. Alternatively, press Alt+Shift+F10, then 0.In the left-hand pane of the run/debug configuration dialog, click Edit configuration templates….
In the Run/Debug Configuration Templates dialog that opens, select a configuration type.
Specify the desired default parameters and click OK to save the template.
Run/debug configuration folders
When there are many run/debug configurations of the same type, you can group them in folders so they become easier to distinguish visually.
Once grouped, the run/debug configurations appear in the list under the corresponding folders.
Create a folder for run/debug configurations
From the main menu, select
. Alternatively, press Alt+Shift+F10, then 0.In the Run/Debug Configurations dialog, select a configuration type and click on the toolbar. A new empty folder for the selected type is created.
Specify the folder name in the text field to the right or accept the default name.
Select the desired run/debug configurations and move them under the target folder.
Apply the changes. If a folder is empty, it will not be saved.
When you no longer need a folder, you can delete it Delete. The run/debug configurations grouped under this folder will be moved under the root of the corresponding run/debug configuration type.
Run/Debug configurations in the Services tool window
You can manage multiple run/debug configurations in the Services tool window. For example, you can start, pause, and stop several applications, track their status, and examine application-specific details.
Add Run/Debug configurations to the Services window
Select
from the main menu or press Alt+8.In the Services tool window, click Add service, then select Run Configuration Type.
Select a run/debug configuration type from the list to add all configurations of this type to the window.
Note that the tool window will only display the configuration types for which you have created one or more configurations.
Run/Debug configuration parameters
Item | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Script path/Module name | Click the list to select a type of target to run. Then, in the corresponding field, specify the path to the Python script or the module name to be executed. | ||||||||
Parameters | In this field, specify parameters to be passed to the Python script. When specifying the script parameters, follow these rules:
In this field you can add a macros to pass various project- or context-specific values when running a run/debug configuration. Click + and select one of the available macros from the list. See Adding macros to run/debug configuration for more details. | ||||||||
Environment | |||||||||
Project | Click this list to select one of the projects, opened in the same PyCharm window, where this run/debug configuration should be used. If there is only one open project, this field is not displayed. | ||||||||
Environment variables | This field shows the list of environment variables. If the list contains several variables, they are delimited with semicolons. By default, the field contains the variable To create a new variable, click , and type the desired name and value. You might want to populate the list with the variables stored as a series of records in a text file, for example:
Variable1 = Value1
Variable2 = Value2
Just copy the list of variables from the text file and click Paste () in the Environmental Variables dialog. The variables will be added to the table. Click Ok to complete the task. At any time, you can select all variables in the Environment Variables dialog, click Copy , and paste them into a text file. | ||||||||
Python Interpreter | Select one of the pre-configured Python interpreters from the list. | ||||||||
Interpreter options | In this field, specify the command-line options 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.
| ||||||||
Add content roots to PYTHONPATH | Select this checkbox to add all content roots of your project to the environment variable PYTHONPATH; | ||||||||
Add source roots to PYTHONPATH | Select this checkbox to add all source roots of your project to the environment variable PYTHONPATH; | ||||||||
Execution | |||||||||
Emulate terminal in output console | Enables running your script or module in the output console with the emulated terminal mode. This mode can be helpful for the tasks that cannot be implemented with the standard output console, for example, when your script performs caret return actions ( Note that emulating terminal in the output console differs from running the Terminal that is a separate tool window used for running system shell commands. | ||||||||
Run with Python console | Enables running your script or module with the Python console. | ||||||||
Redirect input from | Enables redirecting data from a text file to standard input. Use this option if your script requires some input and you want to automatically submit the values instead of typing them in the Run console. To enable redirecting, select the checkbox and specify the path to the target text file. | ||||||||
Docker container settings Click to open the dialog and specify the following settings: | |||||||||
Options |
Click to expand the tables. Click , , or to make up the lists. | ||||||||
Docker Compose | |||||||||
Commands and options | You can use the following commands of the Docker Compose Command-Line Interface:
| ||||||||
Command Preview | You can expand this field to preview the complete command string. Example: if you enter the following combination in the Commands and options field: the preview output should looks as follows:
docker-compose
-f C:\PyCharm-2019.2\Demos\djangodocker-master\docker-compose.yml
-f <override configuration file>
up --build exec --user jetbrains
|