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

181–190 of 202 posts

Re: Python in Visual Studio Code

#181

Post by tracker1 »

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.

Can you get away with just having the terminal open the path in WSL? I'm not sure what your workflow is though. I change mine to use msys bash (installed via git for windows) instead of powershell in windows. Not sure if it'd be too much more difficult to do similar with WSL.

Also, no idea on integrating tasks... Would be nice to see more in the box. Only windows machine I have now is my work laptop, and we're only targeting windows deploys, so cannot answer more specifically.

Re: Python in Visual Studio Code

#182

Post by tracker1 »

vgy7ujm wrote: post #9

We want Perl support!

There are several perl extensions from language support, general debugging etc. Though this can probably be improved, I think it has a lot of the same challenges that Ruby support has. A limited user base, and a comparatively flexible language.

Re: Python in Visual Studio Code

#183

Post by tracker1 »

I tried it first very early on, but was hesitant after trying Brackets and Atom. I was happily surprised and once they added the integrated terminal, I was hooked. I don't use the tasks feature (usually just a terminal or two open). In general it's been incredibly nice though.

Re: Python in Visual Studio Code

#184

Post by lliamander »

Loic wrote: post #147
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 currently switching from emacs to VS Code. I am using an emacs keymap and I must say, it is wonderful. For Python, I can per project easily select the right virtual environment, the "intellisense" like system is working very well, it is pretty fast and you can customize a lot of it. I am expecting to slowly move out of emacs for my coding in the next few months. Emacs will be kept because I have a lot of org-mod…

> So yes, I do think this is the editor which is going to move a lot of old coders out of emacs/vi/vim.

That certainly seems a possibility, though I expect it may be somewhat dependent upon the language used, and whether the community around that language invests enough effort to develop vscode plugins for that language.

Re: Python in Visual Studio Code

#185

Post by gnulinux »

vgy7ujm wrote: post #9

We want Perl support!

Perl is very tricky. Its syntax is undecidable, so unless you run the program it's not possible to construct a syntax tree given input (in the general case, it's possible to make heuristics that will cover 99%) so it requires more brain power compared to easy-to-parse languages like python.

Re: Python in Visual Studio Code

#187

Post by Apaec »

ziftface wrote: post #88
zython wrote: post #54

Earlier quoted context omitted.

Just out of curiosity, what are some of the tasks that you run in vscode ? I've never found a real use for them, so I want to know what other people use them for.

I use them to convert markdown files to pdfs and open them. It can be as simple as the shell command `pandoc .md -o .pdf; open *.pdf`, and for more complicated documents, you can just write a makefile and have vscode use that.

Tmux + vim seems better suited for this task.

Re: Python in Visual Studio Code

#188

Post by Apaec »

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…

Honest question, how can I know if this type of comments are not something like paid advertising more than an honest review?

Most vim users chose it because they're borderline anti-IDEs, it's really strange to me that you chose to switch for features that a vim+tmux workflow already offers.

Re: Python in Visual Studio Code

#190

Post by moises_silva »

johnfn wrote: post #144
moises_silva wrote: post #67

Earlier quoted context omitted.

What vim plugin(s) do you use? I remember installing one but the emulation did not quite work for jumping into code definitions and back (it'd jump, but going back wouldn't work correctly), so I moved back to pycharm for the time being (vim emulation worked better there for me).

Hi, I'm the guy who coded that part of VSCodeVim, and I specifically made it work for that case. gd and ctrl minus should always work to go to definition and back. It's possible you tried it when it wasn't working as well as it does now.

Hey, thanks for your work and for chiming in here! I will give it another shot.
Post reply on HN