Live data from Hacker News

Python in Visual Studio Code

blogs.msdn.microsoft.com

121–130 of 202 posts

Re: Python in Visual Studio Code

#121

What's mind blowing is the community support behind VSCode. If you report a bug, you get a reply in less than 24h, your bug gets tagged, assigned to someone and fixed ASAP. Then you get a new release every month with ton of bug fixes, improvements and new features. Compare that to any other IDE or even any other open source projects.

That... hasn't been my experience: https://github.com/Microsoft/vscode/issues/18549 https://github.com/Microsoft/vscode/issues/16858

Maybe I just care a little too much about code folding, but after origami.el in emacs and atom and vim's great selection of folding commands, it seems like an oversight.

VS Code has also painted itself into a corner making proper vim emulation impossible: https://github.com/Microsoft/vscode/issues/22276#issuecommen...

The editor is awesome, and I'm really thankful for Microsoft's work in this space, especially on the LSP. But it's not everything for everyone.

Re: Python in Visual Studio Code

#122
post #71
post #40

I prefer Atom, but I’ve started having a weird memory leak issue in version 1.29 that prevented me from using it further (note: I’ve disabled all extensions and the problem persists). I use Ubuntu. I’m using VSCode now and it’s good, but I do intend to return to Atom when I get some time to properly create an issue for this problem in GitHub and help the team to fix it.

Since Atom is now owned by Microsoft I am wondering what is going to happen with Atom. Does it get better or does it get cut lose into a "community" project?

Atom and VSCode share lots of common infrastructure and Microsoft is investing heavily in that.

With that, even with no specific efforts toward Atom, it should still see improvements over time.

Re: Python in Visual Studio Code

#123
post #64

Crazy question: Since Microsoft bought GitHub, would it make sense to merge VSCode and Atom at some point, keeping the best of each one?

What's the best of Atom?

As the other comment mentioned, extensibility. Their API is much easier to navigate. Their commands line up exactly with the name that shows up in the fuzzy finder, so dispatching a command or adding a key binding is a breeze. The settings menu supports things like drop down lists and color pickers. The UI is both beautiful and consistent. And Vim Mode Plus feels far ahead of Vscodevim.

You do lose the dedicated python developer, first class LSP support, and integrated debugger though.

Re: Python in Visual Studio Code

#124
Never thought that code editor from the MSFT would become my daily driver IDE.

The only feature I need most from the VSCode (which is not implemented yet) is Python Remote interpreter[1]. While `ptvsd` is more or less convenient for remote debugging, it doesn't help when you need IntelliSense/linting while developing code being interpreted in container/virtual machine/remote host. IntelliJ PyCharm is clearly ahead here for now.

[1] Issue #79: https://github.com/Microsoft/vscode-python/issues/79

Re: Python in Visual Studio Code

#125
post #105

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…

then their management went astray.

That, and Microsoft actively worked to kill them. I don't think JetBrains position is nearly as precarious.

Re: Python in Visual Studio Code

#126
post #118

I'm using VSCode for developing in Elixir and (because I had the license anyway I guess) my Python code in PyCharm. But perhaps I should re-evaluate VSCode for Python as well as it works fantastic (including quite advanced code warnings and errors) for Elixir.

Which Elixir extension are you using for VS Code? Are you on Windows, Linux or Mac?

I've had the best luck with the ElixirLS extension on Linux but there are still a few weird things here or there.

Re: Python in Visual Studio Code

#127
post #72
post #13

Earlier quoted context omitted.

> can benefit one a lot. What are those benefits? I tried to switch from vim to VSCode, and it just felt like it confined me. To be fair, I don't "run vim", per say, I run a shell with tmux inside, split horizontally in two, with vim on top, and two shells (a vertical split) underneath. The left shell on the bottom being used for miscellaneous things, and the right one running some kind of live code checking (with vi…

I could never get used to NERDTree for navigating through my project. What plugin do you use for project navigation?

not op, but i use ctrlp.vim for everything. feels a lot better than most things.

Re: Python in Visual Studio Code

#128
post #45
post #13

Earlier quoted context omitted.

> can benefit one a lot. What are those benefits? I tried to switch from vim to VSCode, and it just felt like it confined me. To be fair, I don't "run vim", per say, I run a shell with tmux inside, split horizontally in two, with vim on top, and two shells (a vertical split) underneath. The left shell on the bottom being used for miscellaneous things, and the right one running some kind of live code checking (with vi…

I mean, it sounds like to me vscode has nothing to offer you, if your desktop (i.e. what we see when we look at your monitor) remains so static (in a positive sense). I find vscode more useful than vim because I can quickly and easily swap out the pieces of environment I need. Need a terminal real quick? Ctrl`, command, ctrl` again and poof it's gone, with nothing in front of me but my code. Need git real quick? Ctrl…

> I find vscode more useful than vim because I can quickly and easily swap out the pieces of environment I need. Need a terminal real quick? Ctrl`, command, ctrl` again and poof it's gone, with nothing in front of me but my code. Need git real quick? Ctrl shift g. Need one more tab? Another? Ctrl \, and so on.

I'm able to do all of these things too with my setup, although it's not vim driving my setup, it's tmux. Using just plain vim doesn't work for me.

> I usually work with three or for different files opened, some tucked away in a tab that I can quickly shift to when I need it. And when I need to get to my "wall o' terminals", I just switch to that workspace (gnome).

Most of the time, I have two files open too, sometimes three. I never use tabs for files though. If I need to work on multiple files, I have them all open in splits. Seems to work fine all the time. I use ctrlp to easily switch between buffers and files.

> Whenever I watch the local vim lady do her thing, it's an entirely different workflow. Grepping across files, then opening one in vim so it just kinda pops up in a new terminal window. Doing a thing there, then closing it to go work in a different vim window... Admirable memory map of the code base and confidence to just close the file and move on, but not for me.

Yeah, doesn't work for me either... My setup looks like this[1] most of the time, and I'm easily to add any and everything as I need it.

[1]: https://imgur.com/a/A9b3izE

Re: Python in Visual Studio Code

#129

I have been following this extension ever since Don Jayamanne joined Microsoft. This has grown by leaps and bounds since then and is a fantastic extension. I was a little leary when I learned they were tossing out jedi in favor of the VS Python language server. However, after playing with it for a month or so now I can tell that it's a drastic improvement over what's currently in place. If anybody from the MS team is…

Jedi provides completions. LS has much wider capabilities - formatting, code rename/refactoring, detecting unused or missing imports, discovering unit tests, linting as you type (so you don't have to run PyLint manually) and more.

Re: Python in Visual Studio Code

#130
post #13

Earlier quoted context omitted.

> can benefit one a lot. What are those benefits? I tried to switch from vim to VSCode, and it just felt like it confined me. To be fair, I don't "run vim", per say, I run a shell with tmux inside, split horizontally in two, with vim on top, and two shells (a vertical split) underneath. The left shell on the bottom being used for miscellaneous things, and the right one running some kind of live code checking (with vi…

Could you expand on what "Your way" is? I really really like VSCode for Python and never had the nerve to learn VIM, so I'm wondering what you do that causes it to be a fight.

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 on basic primitives that all function the same way and you can compose them as you like. It just works. You can't do that with VSCode or any other IDE. They all put limitations on you and if your preference doesn't fit its, you're out of luck.

Post reply on HN