... | @@ -38,7 +38,7 @@ In the following dialog, you can select the path of the Python executable that y |
... | @@ -38,7 +38,7 @@ In the following dialog, you can select the path of the Python executable that y |
|
|
|
|
|
You can either set this path to the system-wide installation of your preferred Python version, or (more commonly) to a project-level virtualenv (see ["Python Virtual Environments"](/virtualenv)).
|
|
You can either set this path to the system-wide installation of your preferred Python version, or (more commonly) to a project-level virtualenv (see ["Python Virtual Environments"](/virtualenv)).
|
|
|
|
|
|
As shown in the following figure, PyCharm will let you navigate graphically the directories of the server and select your preferred Python path. For virtualenvs, the path that must be used is `<virtualenv-root>/bin/python`.
|
|
As shown in the following figure, PyCharm will let you navigate graphically the directories of the server and select your preferred Python path. For virtualenvs, the executable path is `<virtualenv-root>/bin/python`.
|
|
|
|
|
|
<img src="./figures/pycharm3.png" width="300">
|
|
<img src="./figures/pycharm3.png" width="300">
|
|
|
|
|
... | @@ -46,4 +46,13 @@ The figure shows an example for a virtualenv located in the user's home director |
... | @@ -46,4 +46,13 @@ The figure shows an example for a virtualenv located in the user's home director |
|
|
|
|
|
**IMPORTANT:** since the virtualenv is not part of your Python project, differently from your source files, it will not be synchronized automatically between local and remote machine by PyCharm. This means that you should create your virtualenvs in a folder that will *not* be deleted automatically. This is especially important for servers other than philae, where some folders are periodically erased (see ["Storage Management and Quotas"](/storage)).
|
|
**IMPORTANT:** since the virtualenv is not part of your Python project, differently from your source files, it will not be synchronized automatically between local and remote machine by PyCharm. This means that you should create your virtualenvs in a folder that will *not* be deleted automatically. This is especially important for servers other than philae, where some folders are periodically erased (see ["Storage Management and Quotas"](/storage)).
|
|
|
|
|
|
#### Set the Path of the Remote Python Binary |
|
#### Setup Automatic Synchronization of Project Files
|
|
|
|
|
|
|
|
Lastly, you have to setup the automatic synchronization of Python files from your local machine to the remote server. In the window shown in the second figure above, click on the folder icon at the right of "Sync Folders" and then change the "Remote Path" to the path where you want your project files to reside on the server.
|
|
|
|
|
|
|
|
The figure below
|
|
|
|
|
|
|
|
<img src="./figures/pycharm3.png" width="300">
|
|
|
|
|
|
|
|
**IMPORTANT:** the Python virtualenv does *not* need to be in the same folder as your project. In fact, in many cases it could be better to have them in separate folders.
|
|
|
|
|