PyCharm 2017.3 Help

Configuring Remote Interpreters via Vagrant

This feature is only supported in the Professional edition.

The following is only valid when Vagrant Plugin is installed and enabled!

In this section:

Besides that, make sure that the following prerequisites are met (outside of PyCharm):

  • Oracle's VirtualBox is installed on your computer.
  • Vagrant is installed on your computer, and all the necessary infrastructure is created.
  • The parent folders of the following executable files are added to the system PATH variable:
    • vagrant.bat or vagrant from your Vagrant installation. This should be done automatically by the installer.
    • VBoxManage.exe or VBoxManage from your Oracle's VirtualBox installation.
  • The required virtual boxes are created.

Configuring remote Python interpreter via Vagrant

To configure a remote Python interpreter

  1. In the Project Interpreters page of the Settings/Preferences dialog box, click cogwheel framed.
  2. From the drop-down list, choose Add Remote .
    py interpreter types remote

    The dialog box Configure Remote Python Interpreter opens.

  3. In this dialog box, click the radio button Vagrant:
    py configure remote interpreter vagrant

    In this case, the remote server settings are taken from the vagrant configuration file, defined in the page Vagrant.

  4. Click the browse button browseButton next to the field Vagrant instance folder, and specify the desired Vagrant instance folder.

    This results in showing the link to Vagrant host URL.

  5. The Python interpreter path field displays the path to the desired Python executable. You can accept default, or specify a different one.
  6. Click OK in the Configure Remote Python Interpreter dialog box. The configured remote interpreter is added to the list.
  7. Back in the Project Interpreter page, if necessary, configure the path mappings:
    1. Click browseButton:
      py edit path mapping
    2. In the dialog box that opens add (add) or delete (delete) path mappings as desired.
Last modified: 28 March 2018

See Also



Language and Framework-Specific Guidelines: