Run/Debug Configuration: Python
When you run your application for the very first time, PyCharm automatically creates the temporary Run/Debug configuration. You can modify it to specify or alter the default parameters and save it as a permanent Run/Debug configuration.
PrerequisitesBefore you start, ensure that Python and related frameworks are installed.
Refer to their respective download and installation pages for details:
Use this dialog to create a run/debug configuration for Python scripts.
|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.|
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 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 = Value2Just 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.
Select one of the pre-configured Python interpreters from the 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.|
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;|
|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:
Click to expand the tables. Click , , or to make up the lists.
|Commands and options|
You can use the following commands of the Docker Compose Command-Line Interface:
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
|Is Active||Select checkboxes in this column to have the log entries displayed in the corresponding tabs in the Run tool window or Debug tool window .|
|Log File Entry|
The read-only fields in this column list the log files to show. The list can contain:
|Skip Content||Select this checkbox to have the previous content of the selected log skipped.|
|Save console output to file||Select this checkbox to save the console output to the specified location. Type the path manually, or click the browse button and point to the desired location in the dialog that opens.|
|Show console when a message is printed to standard output stream||Select this checkbox to activate the output console and bring it forward if an associated process writes to Standard.out.|
|Show console when a message is printed to standard error stream||Select this checkbox to activate the output console and bring it forward if an associated process writes to Standard.err.|
|Click this button to open the Edit Log Files Aliases dialog where you can select a new log entry and specify an alias for it.|
|Click this button to edit the properties of the selected log file entry in the Edit Log Files Aliases dialog.|
|Click this button to remove the selected log entry from the list.|
|Click this button to edit the select log file entry. The button is available only when an entry is selected.|
When you edit a run configuration (but not a run configuration template), you can specify the following options:
Specify a name for the run/debug configuration to quickly identify it when editing or running the configuration, for example, from the Run popup Alt+Shift+F10.
Allow parallel run
Select to allow running multiple instances of this run configuration in parallel.
By default, it is disabled, and when you start this configuration while another instance is still running, PyCharm suggests to stop the running instance and start another one. This is helpful when a run/debug configuration consumes a lot of resources and there is no good reason to run multiple instances.
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.
|Alt+Insert||Create a run/debug configuration.|
|Alt+Delete||Delete the selected run/debug configuration. Note that you cannot delete default configurations.|
|Ctrl+D||Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.|
|The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.|
|View and edit the template (that is, the default run/debug configuration settings). The templates are displayed under the Templates node and used for newly created configurations.|
Move the selected run/debug configuration up and down in the list.
The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration.
Default templates of run/debug configurations are always sorted alphabetically.
Move into new folder / Create new folder. You can group run/debug configurations by placing them into folders.
To create a folder, select the configurations within a category, click , and specify the folder name. If only a category is in focus, an empty folder is created.
Then, to move a configuration into a folder, between the folders or out of a folder, use drag or and buttons.
To remove grouping, select a folder and click .
|Click this button to sort configurations in the alphabetical order.|
In this area you can specify tasks that must be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
Click this icon to add one of the following available tasks:
|Alt+Delete||Click this icon to remove the selected task from the list.|
|Enter||Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.|
|/||Alt+Up/Alt+Down||Click these icons to move the selected task one line up or down in the list. The tasks are performed in the order that they appear in the list.|
|Show this page||Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.|
|Activate tool window|
Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5.