Remote Interpreter path mapping after Deployment root change in PyCharm 2024.x

Direct answer

No. Changing the Deployment server root path in PyCharm 2024.x does not automatically propagate to the Remote Interpreter’s path mappings. The two configurations are stored independently; PyCharm provides no built‑in mechanism that copies Deployment > Mappings changes into the interpreter settings. You must update the Remote Interpreter path mappings manually after any Deployment root change.

Why the discrepancy occurs

Deployment configuration (Settings → Build, Execution, Deployment → Deployment) governs file transfer — which local folders are uploaded to which remote folders. The Remote Interpreter configuration (Settings → Project → Python Interpreter → gear icon → Show Path Mappings) governs import resolution — how the remote Python process translates local source paths to remote module locations. PyCharm treats them as separate concerns and does not link them internally.

Verification & synchronization steps

1. Record the current Deployment root. Open Settings → Build, Execution, Deployment → Deployment, select the server, and note the Root path value (e.g., /home/user/project_v2).
2. Inspect the interpreter mappings. Open Settings → Project → Python Interpreter, choose the remote interpreter, click the gear icon, and select Show Path Mappings. List every local → remote pair.
3. Align each remote path with the Deployment root. For every mapping, ensure the remote path starts with the Deployment root from step 1. If the Deployment root changed from /home/user/project to /home/user/project_v2, edit each remote path accordingly (e.g., change /home/user/project/src → /home/user/project_v2/src).
4. Validate with a runtime test. Create a temporary script in the project root:

   import sys
   print('\n'.join(sys.path))
   import your_package  # replace with a real module
   print('Import OK')

   Run it on the remote interpreter. Successful execution without ModuleNotFoundError confirms the mappings are correct.
5. Invalidate caches if imports still fail. File → Invalidate Caches / Restart → Invalidate and Restart. The remote interpreter caches path mappings at startup.

Known boundaries & caveats

• Deployment success logs ≠ import health. The Deployment tool window only reports file‑transfer completion. It does not verify that the remote interpreter’s sys.path reflects the new root.
• No documented propagation API. JetBrains documentation (as of 2024.x) describes Deployment and Remote Interpreter as independent features with no automatic synchronization.
• Container‑based interpreters differ. If the remote interpreter is configured via Docker, WSL, Vagrant, or SSH‑with‑Docker, the path‑mapping UI and synchronization behavior are distinct. The steps above apply to a classic SSH/SFTP Remote Interpreter.

One diagnostic detail needed

Which interpreter type are you using? (Classic SSH/SFTP Remote Interpreter, Docker, WSL, Vagrant, or SSH‑with‑Docker?) The verification steps are identical, but the mapping UI and cache‑invalidation behavior can vary by interpreter technology.