Migrate from Visual Studio Code

To import a Python project created in Visual Studio Code, just open the project directory in PyCharm:

PyCharm searches for a virtual environment in the source directory. If detected, the virtualenv interpreter is configured automatically.

If no environment is detected, PyCharm sets up the system interpreter for the project.

For information about configuring other types of Python interpreters, refer to one of the following sections:

• Configure a pipenv environment

• Configure a Poetry environment

• Configure a conda virtual environment

• Configure an interpreter using WSL

• Configure an interpreter using Vagrant

• Configure an interpreter using SSH

• Configure an interpreter using Docker

• Configure an interpreter using Docker Compose

If the imported project does not contain a virtual environment, you can configure a new Python interpreter, and then install the required packages for it:

• For conda and virtualenv environments, you can install the required packages from requirements.txt.

  You can also create a virtualenv environment using requirements.txt.

• For pipenv environments, enable the Install packages from Pipfile checkbox when creating the environment, or create an environment using the Pipfile.

• For Poetry environments, enable the Install packages from pyproject.toml checkbox when creating the environment, or create an environment using pyproject.toml.

At the moment, PyCharm doesn't support importing run/debug configurations from launch.json. You will need to create a run/debug configuration for your project manually:

Here is how the most common launch.json attributes can be converted into parameters when creating a run/debug configuration:

name

The name of the run/debug configuration.

Specify it in the Name field.

type

The type of the run/debug configuration.

Select the corresponding type when creating the configuration.

request

Specifies whether to launch a program in debug mode or attach the debugger to an already running program.

For "request": "launch", you do not need to set any configuration parameters.

If your configuration contains "request": "attach", you cannot create a similar run/debug configuration in PyCharm. For information, refer to Attach to process.

program

Executable or file to run when the configuration is launched.

Select a type of target to run from the dropdown. Then specify the path to the Python script or the module name to be executed.

cwd

Current working directory for finding dependencies and other files.

Specify it in the Working directory field.

args

Arguments passed to the program when running or debugging it.

Specify the arguments in the Script parameters field. In this field, you can use macros which correspond to variables in Visual Studio Code configuration files. For information, refer to Pass parameters to the running script.

env

Environment variables.

Specify the environment variables in the Environment variables field. For information, refer to Run/debug configurations.

envFile

Path to dotenv file with environment variables.

Copy the environment variables from the specified file to the Environment variables field. For information, refer to Run/debug configurations.

console

Console to use for running or debugging the program.

In PyCharm, code is usually executed in the Run tool window. When debugging, the Debug console is opened by default. However, you may want to specify other execution options. For information, refer to Run/debug configurations.

justMyCode

When omitted or set to true, debugging is restricted to user-written code only.

In PyCharm, you can configure that by enabling or disabling the Do not step into library scripts checkbox in Settings | Build, Execution, Deployment | Debugger | Stepping. For information, refer to Step into.

The table below shows how the top Visual Studio Code actions (and their shortcuts) are mapped to PyCharm (you may want to print it out to always have it handy).

note

If you choose a keymap specific to your operating system (Default for Windows/Linux or macOS for macOS), there may be conflicts between shortcuts used in PyCharm and your OS. To avoid such conflicts, we recommend tweaking your OS shortcut settings (refer to Keymap for more details).

VSCode keymap

If you prefer not to learn new shortcuts, you can install the VSCode Keymap plugin. It will add the VSCode keymap to PyCharm, which closely mimics the Visual Studio Code shorcuts.

Find action

When you don't know the shortcut for some action, try using the Find action feature available via . Start typing to find an action by its name, see its shortcut, or call it: