MS totally dominates tooling. I am so happy with vs code, use it for my angular development as well.
Use it for Rails and Flutter too here, and really happy with it!
Python in Visual Studio Code
21–30 of 202 posts
Re: Python in Visual Studio Code
#22I am somewhat embarrassed, but also relieved to admit that I switched from vim (nvim to be precise) to VSCode (OMG M$FT!) and am very happy about it. I still use vim bindings as much as I can, but I guess giving up a bit of ideology can benefit one a lot. Although, that is until I start running out of memory on my personal laptop, then it's back to the terminal!
The vscode vim bindings are atrocious. I use them because there's nothing better, but they're bad . Slow, super buggy, and did I mention slow? I hit tab and sometimes instead of inserting a \t, it inserts the letters " ". And it re-runs mypy/flake8/etc whenever I enter or exit insert mode, which I do a ton... so my CPU is constantly pegged. And commands like "2d}" don't delete the correct amount of paragraphs. And on…
i agree with these observations
Re: Python in Visual Studio Code
#23Tried to use python within vscode last month, it works fine, but I still have to hack around for my own workflow.
I eventually switched to pycharm for its autocompletion, class help, even pipenv support natively built-in.
for html/css/js I keep using vscode though.
there is no such thing called universal editor, I still have to use various(vim,geany,vscode,pycharm...) for different scenarios, which is fine but just very time consuming
Re: Python in Visual Studio Code
#24I'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 see if the plugin cache needs an update one way or the other - and runs my aliases (see below).
I have global tasks that now link into workspaces, pretty decent python, golang, and c++ support. I've mapped keys to the 'wierd' collection of things I do between terminator terminals, vim tabs, and whatnot... honestly, it's pretty good. It's not great, the things in 'vim' support are really 'vi'-light. I'd be much happier if vim support meant understanding my .vim hierarchy - but I'm happy.
# vscode bash bits alias vspluginsave="code --list-extensions | xargs -L 1 echo code --install-extension > .vscode.plugins" alias vspluginload="sh ~/.vscode.plugins" alias vspluginclean="rm -rf ~/.vscode/extensions"
Re: Python in Visual Studio Code
#25I am somewhat embarrassed, but also relieved to admit that I switched from vim (nvim to be precise) to VSCode (OMG M$FT!) and am very happy about it. I still use vim bindings as much as I can, but I guess giving up a bit of ideology can benefit one a lot. Although, that is until I start running out of memory on my personal laptop, then it's back to the terminal!
I would really love to ditch more of my nvim setup for vscode, but this bug [1] from 3 months ago absolutely wrecks my productivity. I rely on splits as the primary means to navigate the codebase and having a single cursor position per file is maddening! The vim bindings aren't perfect and are sometimes slow (you can see a macro insert things character by character) but about on-par with IdeaVim for the IntelliJ side…
Yeah VSCode for Vim feels like they are slowly trying to implement a subset for VSCode. This kind of iterative approach doesn't strike me as a way to build something that will finally "feel right", and overcome these limitations. Perhaps some remote vim running actual nvim code with a minimal API bridge into VSCode is more appropriate?
Re: Python in Visual Studio Code
#26Tried to use python within vscode last month, it works fine, but I still have to hack around for my own workflow. I eventually switched to pycharm for its autocompletion, class help, even pipenv support natively built-in. for html/css/js I keep using vscode though. there is no such thing called universal editor, I still have to use various(vim,geany,vscode,pycharm...) for different scenarios, which is fine but just v…
You also have that in VSCode you just need to install the Python plugin. You can do automated visual flake8 linting as well.
Re: Python in Visual Studio Code
#27Vscode 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 Dev setup which is all docker+python. Works beautifully (debugger and all)
Re: Python in Visual Studio Code
#28Updated to the August release of VSCode this morning and discovered that debugging python in the editor is broken. The editor refuses to recognize PYTHONPATH specified in the environment or a .env file. (This refers to VSCode on Windows 10). The hack to work around this is to specify it in the launch.json file. Otherwise I absolutely love VSCode and particularly the Python extension.
Re: Python in Visual Studio Code
#29Earlier quoted context omitted.
The vscode vim bindings are atrocious. I use them because there's nothing better, but they're bad . Slow, super buggy, and did I mention slow? I hit tab and sometimes instead of inserting a \t, it inserts the letters " ". And it re-runs mypy/flake8/etc whenever I enter or exit insert mode, which I do a ton... so my CPU is constantly pegged. And commands like "2d}" don't delete the correct amount of paragraphs. And on…
Which extension do you use? I don’t use vim mode myself but I vaguely remember seeing a conversation about how, for some reason, the better vim plugin with the most favorites doesn’t appear on the top of the search results, and an inferior one is there instead.
I've tried just about every single one and the best one is still the main one. It gets better just about every release similar to VSCode. Not saying it's perfect, but with all of the other VSCode benefits I find it so much better for productivity than plain Vim.
Re: Python in Visual Studio Code
#30I 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.