#PYCHARM REMOTE DEVELOPMENT SOFTWARE#
#PYCHARM REMOTE DEVELOPMENT SERIES#

#PYCHARM REMOTE DEVELOPMENT SOFTWARE#

I also do a ton of software development and machine learning work in Python now and have never managed to move away from Pycharm even though I'd love to be able to have a good enough experience in Vscode so that I could make the switch from Pycharm (the remote development experience in vscode is really neat which is what attracts me). Not the person you replied to, but I love vscode from when I did a bunch of React + JS stuff a few years back.

Is what I want possible? Everything I tried seem to result in my laptop Pycharm setting up a new project somewhere on my Ubuntu box where it would SFTP my project files to, but that resulted in a duplicate of my repo in some other location, which is not what I want. In contrast, every time I tried mimicking this in Pycharm (the paid version), it seemed like there was no way to link my already cloned repos on the Ubuntu box to my local version on my laptop so that work I did locally would always also be 'live' on my Ubuntu box so that were I to VNC into my Ubuntu box and open the same project in my local Pycharm IDE, it would exactly mirror the state of my Pycharm IDE on my laptop. Everything is super snappy and even my bash sessions have the correct remote venvs activated correctly. I can setup SSH access to my box and have an open project for the same repos that I have cloned locally on my Ubuntu box and it's as if I am working on it natively. The vscode experience is pretty fantastic. But when I work from home, VNC feels a bit too sluggish and remote development would be much better for me.

I have all my repos cloned locally and work on various projects locally (and Pycharm is my IDE of choice on the Ubuntu box). My use-case where Pycharm feels a bit deficient is that I have an Ubuntu deeplearning box at work that I can VNC into and develop on whenever needed. My main reason for wishing to be able to switch to Vscode instead of Pycharm is because vscode's remote development UX is really really nice and works a lot better for me compared to the Pycharm way of SFTP-ing files between your local and the remote. This won't replace print statements 100% of the time, because it might be simpler to print a bunch of logs to see where the problem is than to step through the program in the debugger use it when you know where the problem probably is but not what it is. Key commands I use while in pdb: ? for help n to run the next line s to step into the next function call w to see where I am in the stack u and d to go up and down the stack unt to run until a new line is reached (if you're stuck in a loop) interact to go to a normal python shell (if the pdb shell is confused by what you typed).

#PYCHARM REMOTE DEVELOPMENT SERIES#

It basically just collapses a series of 'add print statement and run' into a much tighter loop, which can save a ton of time depending how long it takes your program to throw the error and how many print statements it was going to take you to figure out what was wrong. It drops you into a REPL at that point in the code, and you can then print values and try running things. For me the next step after print debugging was adding an `import pdb pdb.set_trace()` shortcut to my editor (I use 'pdb' as the shortcut, but whatever works.) Do that whenever you would add a print statement and re-run to resolve a confusing bug.

Pycharm remote development