Re:Python in Visual Studio Code – April 2019 Release
by icegreentea2 on Wednesday April 24, 2019 @09:02AM
(#19737885)
I would also like this. Like the sibling, I use Pycharm for this specific use case (as in 95% of my work is in vscode, and I drop into pycharm when I need remote interpreter support).
The github issue tracking this feature is here: https://github.com/Microsoft/vscode-python/issues/79
Unfortunately there's no major activity on it as of late... but I usually go take a peak every few months and hope...
Re:Python in Visual Studio Code – April 2019 Release
by ambivalence on Wednesday April 24, 2019 @09:17AM
(#19737988)
In my time at Facebook that was the killer feature of Nuclide which switched most people to Atom. Ironically, the remote debugger was based on the Visual Studio Tools for Python one.
Re:Python in Visual Studio Code – April 2019 Release
by brento on Wednesday April 24, 2019 @08:55AM
(#19737826)
I run PyCharm using my docker-compose environment, which works great. A co-worker said he was able to get VSCode working with docker-compose, but the setup wasn't easy. He said something about having to attach to the running docker/python process.
Re:Python in Visual Studio Code – April 2019 Release
by abhishekjha on Wednesday April 24, 2019 @09:46PM
(#19744296)
Hi.
Can you elaborate a little more on how you use pycharm with docker-compose and what are the advantages? I am new to all this and I have been using Pycharm quite a lot lately but looking at people’s responses above it feels like I am missing something. Why would you need to connect remotely or where/why does docker fit into this? Isn’t is just an IDE that you install to code/debug?
Sorry in advance if these questions sound a little too primitive.
Thanks.
Re:Python in Visual Studio Code – April 2019 Release
by manojlds on Thursday April 25, 2019 @01:23AM
(#19745264)
You can have pycharm on your machine but the actual python interpreter and the dependencies are in a docker container. This means that you don't 1) install python and dependencies needed for your project in your machine directly 2) reuse the docker container setup that is used for say ci and even production deployment while you are doing development.
Re:Python in Visual Studio Code – April 2019 Release
by mikece on Wednesday April 24, 2019 @09:11AM
(#19737944)
Do you mean connecting a debugger to run/evaluate code in a Docker container? Because I'm pretty sure VSCode does this... or at least I thought it did. (Or is this a feature reserved to full Visual Studio?)
Re:Python in Visual Studio Code – April 2019 Release
by arriu on Wednesday April 24, 2019 @09:57AM
(#19738368)
I was going to post the same comment. This is great but I don't actually know anyone who is running django code outside docker at this point.
Re:Python in Visual Studio Code – April 2019 Release
by sandGorgon on Wednesday April 24, 2019 @10:00AM
(#19738398)
same here - although there is a workaround.
https://github.com/Microsoft/vscode-python/issues/79#issueco...
Re:Python in Visual Studio Code – April 2019 Release
by leadingthenet on Wednesday April 24, 2019 @08:59AM
(#19737862)
As an aside, you can easily do this with PyCharm. It even works with vagrant images.
Re:Python in Visual Studio Code – April 2019 Release
by smnrchrds on Wednesday April 24, 2019 @09:12AM
(#19737954)
This is true, but unfortunately only for the paid version.
Re:Python in Visual Studio Code – April 2019 Release
by JaimeThompson on Wednesday April 24, 2019 @10:57AM
(#19738960)
A year subscription for the individual use license from PyCharm is 89.00 for the first year, 71.00 2nd year, 53 3+ years (all prices in USD) so it isn't a major expensive to get a license.
The only way I have found this possible is to actually run VSCode itself in docker.