Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Python in Visual Studio Code

blogs.msdn.microsoft.com

Post reply on HN
Print view View original

191–200 of 202 posts

Re: Python in Visual Studio Code

#191

Post by bigpeopleareold »

outworlder wrote: post #149
lliamander wrote: post #138

Earlier quoted context omitted.

Interesting how many people have switched from vi/vim to vscode. Does anyone have stories of making a similar switch from emacs? I currently use intellij for java work (because my employer pays for the license) but for most any other type of editing I use emacs. I'd be interested to see what other emacs users think of vscode.

I am still faithful to my Emacs, but Visual Studio Code is this beautiful thing I can't take my eyes off. As an editor, VSCode is still inferior (but improving at lightspeed). As an out-of-the-box experience, it blows almost everything else out of the water. Against my customized Spacemacs, it's still struggling. But that renderer is gorgeous!

I had to start using vscode at a certain level because .net core doesn't have a free debugger (as it seems.) I would have to study vscode-omnisharp source to get a clue how the debugger actually works to use it in emacs - something I don't have time for.

But I started to use it more because the autocompletion is nice. It's not perfect, but out-of-the-box experience is nicer.

After a few months though working in it, I want to go back to Emacs, and as such, Emacs is usually running. Magit for example, or being able to split your screen up as needed, or quickly jumping between files, etc. is something that is burnt into my brain. VScode is terrible at these things.

I am watching the lsp-mode and lsp-ui projects. They seem promising because it answers a concern I have : I need to float between projects in different languages and want the typical set of IDE-like features in each one. It would be nice to have a single set of keybindings regardless of language, which vscode excels at now. VScode has a good debugging story out-of-the-box lsp-ui is promising because it is implementing vscode-like features (like peek mode).

Re: Python in Visual Studio Code

#192

Post by sandGorgon »

joewrong wrote: post #106
sandGorgon wrote: post #27

Vscode has been the first editor that I switched to from vim in 20 years (and yes I went through sublime, atom,etc). A Microsoft editor on Linux... imagine that. Lots of people in my workplace have switched to using vscode from pycharm. They still use pycharm once a month to do a global lint analysis or some tricky refactor...but for daily use, it's much more pleasant to use vscode . In fact, we use vscode with our D…

Any tips to share on debugging python in a docker container using vscode? I've tried their instructions for ptvsd before and after this update but still haven't been able to use the debugger with docker.

you're in luck. I posted this just 2 days back

https://github.com/Microsoft/vscode-python/issues/79#issueco...

Re: Python in Visual Studio Code

#193

Post by fredsir »

shriek wrote: post #159
fredsir wrote: post #130

Earlier quoted context omitted.

Well, the setup I mostly use looks like this: https://imgur.com/a/A9b3izE I've tried getting something like that going in VSCode, but even just switching between terminals and compiling and so on is just too confining. Whenever I've tried, there's always some part of it that doesn't let me easily do something, because it expects one to use it some other way. With a shell, tmux, vim and other CLI tools, it's all based…

This is pretty much why I haven't moved fully to VSCode as well. I gave it a try but I realized that my whole workspace is in terminal. Also, like you said the tools I have compliment to one another very well making it very flexible. The only thing I do miss when working in terminal is that whenever I'm working in markdown I wish it had dead simple preview like that in VSCode.

I do all my document-making in emacs with org-mode and evil (vim-mode). Seriously, it's amazing. When you are done, you are one command away from having it in markdown/pdf/latex/html/word or any other format you can imagine.

I'd love if I could have the same power for managing my todos, tasks, projects, taking notes, README writing, overall agenda with vim, but I can't, so I find it's easily worth it just to use emacs and org.

Here is an example of what you are able to do with emacs and org: https://imgur.com/a/3rTNVYE

And if you need it in markdown, you just manually export it, or set up a hook that does it for you every time the document changes.

And no, the result of the code-blocks in the screenshot is not something I manually inserted into the notes. Org runs the code and inserts the result for me automatically.

Re: Python in Visual Studio Code

#194

Post by mercer »

lliamander wrote: post #138
cik wrote: post #24

I've been using VI since the 90's and VIM since... well the 90's. VSCode is the first IDE I've been able to live, and happily. It blows my mind. I have a tonne of tooling around automated python environments, vim plugins (now vscode plugins), tasks - and it's made the whole thing significantly more 'unixy' than it was before. And to think - MSFT! I have git hooks for my homedir's dotfiles that automatically look to s…

Interesting how many people have switched from vi/vim to vscode. Does anyone have stories of making a similar switch from emacs? I currently use intellij for java work (because my employer pays for the license) but for most any other type of editing I use emacs. I'd be interested to see what other emacs users think of vscode.

Well, my story is that I switched to emacs mostly because org-mode and the decent Vim support that Spacemacs offered. While I tried doing my development in Emacs too, I ended up using VSCode for most of that.

One reason is that I kind of like the separation between Emacs for org-mode and another tool for development.

Another is that VSCode just kind of 'clicks' with my approach. As a freelancer, I often work on multiple projects at the same time. I can have various VSCode projects open, each with its own terminal processes.

I find myself still using Emacs for TRAMP stuff (remote SFTP editing of files) occasionally, but somehow using Emacs for properly working on projects never quite 'clicked' the way VSCode did. It's possible that I just haven't gotten comfortable enough with it yet, but so far I'm really loving the Emacs/VSCode setup. And I still occasionally use Sublime Text for one-off editing of bigger files.

Re: Python in Visual Studio Code

#195

Post by shriek »

fredsir wrote: post #193
shriek wrote: post #159

Earlier quoted context omitted.

This is pretty much why I haven't moved fully to VSCode as well. I gave it a try but I realized that my whole workspace is in terminal. Also, like you said the tools I have compliment to one another very well making it very flexible. The only thing I do miss when working in terminal is that whenever I'm working in markdown I wish it had dead simple preview like that in VSCode.

I do all my document-making in emacs with org-mode and evil (vim-mode). Seriously, it's amazing. When you are done, you are one command away from having it in markdown/pdf/latex/html/word or any other format you can imagine. I'd love if I could have the same power for managing my todos, tasks, projects, taking notes, README writing, overall agenda with vim, but I can't, so I find it's easily worth it just to use emac…

Okay you convinced me with that org-mode. I've already invested huge time learning vim and hopefully it translates well in evil.

Edit: Ah, I see emacs has it's own terminal which is why it was able to support charts and graphs.

Re: Python in Visual Studio Code

#196

Post by zahrc »

bsaul wrote: post #30

I wonder how intellij will survive if vscode becomes a standard for pretty much every language. Which makes me wonder if kotlin will also survive if intellij goes bankrupt.

IntelliJ (Ultimate at least) is miles ahead in comparison to VSCode. Adding, configuring and managing frameworks is a lot easier right now.

Also, don't forget Android studio is built on IntelliJ.

I am scared that it will end in an endless discussion á la "vim vs Emacs" somewhen.

I think jetbrains will do just fine.

Re: Python in Visual Studio Code

#197

Post by pvg »

pjmlp wrote: post #177
pvg wrote: post #176

Earlier quoted context omitted.

HN loves to hate Microsoft It'd be nice if you saved this stuff for when you're replying to HN, not to me. Microsoft in the 80s and 90s were hyper-aggressive towards anyone they considered a key competitor and played dirty. The fact that some of these competitors didn't do themselves any favours doesn't change that (I think, quite uncontroversial) fact. I don't think VS Code is this huge threat to Jetbrains and as a…

Quick Pascal, Quick Basic, MASM, Microsoft C and the 16 bit versions of Visual C++ were hardly hyper-aggressive products, versus the competition. They were aggressive with MS-DOS and Windows, their developer tools not really, even with VB and VC++ 32, they started to win when Watcom, Borland, CA, Zortech, Symantec Metrowerks stopped being worthwhile to spend money on.

We're getting a bit into the weeds here but I think it's a mistake to conflate the 'aggression' part of this with the quality of the products. In fact, the poor quality of the products was part of the aggression - Microsoft got to leverage its position as the platform vendor against its own ISVs. They even named them with Borland's own naming scheme!

You can probably make a decent argument that Borland's mismanagement was a misguided attempt to respond to Microsoft's pressure.

Re: Python in Visual Studio Code

#198

Post by Too »

pjmlp wrote: post #105
jbigelow76 wrote: post #100

Earlier quoted context omitted.

Opera was a one trick pony, Jetbrains seems to be decently diversified in the products they offer that covers a large number of developer users and development stacks. That's not to say it doesn't hurt but their situation isn't as dire as Opera's was.

Back in the 90's Borland seemed to have no match for developer tools, then their management went astray. And to be honest I never understood the complaint about lack of quality of their documentation vs what Microsoft, Zortech, Watcom, Nantucket and others used to have on those days. Currently JetBrains is segmenting their products, for example native code languages are only supported in Clion/AppCode, even if you bu…

Jetbrains product segmenting is a bit strange yes. Right now as a full stack developer i have three options: 1. One instance of VSCode with a few plug ins for each language, 2. IntelliJ ultimate €499/year/seat, 3. Run four free IDEs from jetbrains simultaneously.

#2 is too expensive, #3 is too inconvenient and while #1 isn't as good as jetbrains it's too good enough to justify an upgrade to intellij ultimate. If you are saying native is not even supported in Ultimate this makes things even worse. Jetbrains should release something cheaper in between #2 and #3 that supports many languages but maybe hold back on certain premium features like profiling etc.

Re: Python in Visual Studio Code

#199

Post by chomp »

rcarmo wrote: post #165
chomp wrote: post #15

Need WSL support for the Python extension! Right now it's impossible to use the Python extensions from within the WSL environment.

I'm on the same boat, since I only use pyenv inside WSL. It's something that is being discussed (and worked on for other languages). The relevant issue is at: - https://github.com/Microsoft/vscode-python/issues/67 And the VS Code team was asking for folk to interview regarding WSL integration: https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGG... (Full disclosure: I work at Microsoft, but in other teams, an…

Cool thanks, I filled out the form!

My uses are a bit mundane but I'm willing to talk about them!

Re: Python in Visual Studio Code

#200

Post by irlib »

lliamander wrote: post #138
cik wrote: post #24

I've been using VI since the 90's and VIM since... well the 90's. VSCode is the first IDE I've been able to live, and happily. It blows my mind. I have a tonne of tooling around automated python environments, vim plugins (now vscode plugins), tasks - and it's made the whole thing significantly more 'unixy' than it was before. And to think - MSFT! I have git hooks for my homedir's dotfiles that automatically look to s…

Interesting how many people have switched from vi/vim to vscode. Does anyone have stories of making a similar switch from emacs? I currently use intellij for java work (because my employer pays for the license) but for most any other type of editing I use emacs. I'd be interested to see what other emacs users think of vscode.

My story was: vim (5 years) -> emacs (7 years) -> sublime (2 years) -> atom (1 year) -> vscode (2 years and counting).

Switch from vim to emacs is obvious. Switch from emacs to sublime was triggered by moving from Linux to MacOS (my Thinkpad was failing after diving in a tropical rain so I bought a brand new MacBook).

Post reply on HN