PyCharm Edu 2018.3 Help


With the Mercurial integration enabled, you can perform basic Mercurial operations from inside PyCharm Edu.

In this section:



  • Mercurial is installed on your computer.

  • The location of the Mercurial executable file hg.exe is correctly specified on the Mercurial page of the Settings/Preferences dialog box.

    If you followed the standard installation procedure, the default location is /opt/local/bin or /usr/local/bin for Linux and macOS and /Program Files/TortoiseHG for Windows.

    It is recommended that you add the path to the Mercurial executable file to the PATH variable. In this case, you can specify only the executable name, the full path to the executable location is not required.

  • Mercurial integration is enabled for the current project root or directory.

If you want to use a remote repository, create a Mercurial hosting account first. You can access the remote repository through a pair of ssh keys or apply the username/password and keyboard interactive authentication methods supported by the Mercurial integration.

Mercurial support

  • When Mercurial integration with PyCharm Edu is enabled, the Mercurial item appears on the context menus of the Editor and the Project Tool Window.

  • The files in the folders under the Mercurial control are highlighted according to their status. See File Status Highlights for file status highlighting conventions.

  • Modifications results are shown in the Version Control tool window.

  • When using Mercurial integration, it is helpful to open the Version Control tool window. The Console tab displays the following data:
    • All commands generated based on the settings you specify through the PyCharm Edu user interface.

    • Information messages concerning the results of executing generated Mercurial commands.

    • Error messages.

Note that it is possible to access the desired VCS commands from the Search for a target by name window.

For example, press Ctrl+Shift+A and start typing the desired command name:

pe access to commands
Last modified: 29 June 2019