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

Python in Visual Studio Code – April 2019 Release

devblogs.microsoft.com

Post reply on HN
Print view View original

21–30 of 42 posts

Re: Python in Visual Studio Code – April 2019 Release

#21

Post by azhenley »

jaabe wrote: post #19
jjuel wrote: post #13

Microsoft is doing a good job of turning VSCode into Visual Studio. This is far from a basic text editor anymore.

Which is honestly what they need to do, to make .net core truly next level. It was such a drag to so C# on non windows machines, and it’s becoming less and less so. Visual Studio still has some perks, but with the dotnet cli it’s actually decent enough to use .net core on a Mac. What I don’t get is why they aren’t focusing even more on VS Code, I mean, why bother making Visual Studio for mac when you have an all-plat…

I agree. I always kept a Windows VM on my Mac so I could use Visual Studio. About 6 months ago I uninstalled it and just use VS Code now (though my C# usage has also decreased).

I've heard great things about JetBrains Rider but haven't tried it.

Re: Python in Visual Studio Code – April 2019 Release

#22

Post by arriu »

manojlds wrote: post #3

A feature I would like is use my VScode against a python programming environment in docker. The only way I have found this possible is to actually run VSCode itself in docker.

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

#23

Post by SketchySeaBeast »

jjuel wrote: post #20
jaabe wrote: post #19

Earlier quoted context omitted.

Which is honestly what they need to do, to make .net core truly next level. It was such a drag to so C# on non windows machines, and it’s becoming less and less so. Visual Studio still has some perks, but with the dotnet cli it’s actually decent enough to use .net core on a Mac. What I don’t get is why they aren’t focusing even more on VS Code, I mean, why bother making Visual Studio for mac when you have an all-plat…

Yeah never said it was a bad thing. I love VSCode and I like Visual Studio. I wish VSCode could replace Visual Studio for my current work, but I don't think it works well with .NET Framework solutions yet (and may never will).

I find it's not as turn key as Visual Studio. It has a lot of the same, or even better and different functionality, but if I'm opening and new solution, 99/100 times if I want to run it immediately without tinkering it'll be in Visual Studio. I love code for the extensions, but Visual Studio still feels easier to get something up and running in.

Re: Python in Visual Studio Code – April 2019 Release

#24

Post by sandGorgon »

manojlds wrote: post #3

A feature I would like is use my VScode against a python programming environment in docker. The only way I have found this possible is to actually run VSCode itself in docker.

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

#25

Post by kbumsik »

Great new features, though it's a little bit shame that we still need to import a .ipynb file manually to work with it (I know it is not the VScode team's fault).

I really wish that the Jupyter community would consider re-design .ipynb file format, such as separating a source code (cells) as a file and stopping using JSON format.

The current .ipynb file format is highly against modern software engineering. Since it contains everything inside of a single file including giant binaries, it is almost impossible to properly version control, and there is no point of using human-readable JSON format because its content is already not human-readable.

Re: Python in Visual Studio Code – April 2019 Release

#26

Post by benjaminjackman »

Overall I really like this extension and especially its interactive programming / notebook features. I am a big fan of jupyter notebooks, and wrote my own version for Scala (it was more inspired by Mathematica since Juypter didn't exist yet) a long long time ago.

However having all the output be in a dedicated window as this extension does, that allows for scrolling back in the order things were run rather than in the order they are laid out in the notebook is turning out to be better for some use cases. Also, it allows having the output side-by-side which takes better advantage of the horizontal to vertical pixel ratio of monitors.

Another thing I like is that editing cells as plain text using #%% to separate them is just a better more intuitive interface for a programmer than having a bunch of separate text-areas (imho). And it nicely dodges all the padding and unnecessary white-space problems that a Jupyter notebook has compared to a mathematica one, allowing more information to fit on the screen.

For one downside: I haven't ever used an extension that is so inclined to randomly pop up with tips and surveys while I am programming as this one. It's incredibly annoying and I've spent a lot of time trying to figure out how to disable it. Including looking through the code on github, but don't see anyway at all to do it.

It's a catch-22 situation because VS Code doesn't have the option to disable notifications like these, the person in charge of deciding if there should be a feature to prevent popups says that it's an extension issue and to take it up with them. And the extension clearly doesn't have the mindset that it is an issue and frankly I don't think it's an extensions job to re-invent the wheel on this every time so I don't blame them. They are using the tools they have as extension authors because it's clearly not the extensions job to set the style of of notification deliver to the user, only that there is one to present, perhaps with an associated urgency level. The IDE ought to then deliver it in the manner most desired by it's user.

Contrast this with Intellij which works around all of this by simply having a thought out system for notifications, wherein the user, can force them all to go to a log in a panel without a popup, which, for me is great because I'm coding, don't knock me out of the zone!

Re: Python in Visual Studio Code – April 2019 Release

#27

Post by jaabe »

SketchySeaBeast wrote: post #23
jjuel wrote: post #20

Earlier quoted context omitted.

Yeah never said it was a bad thing. I love VSCode and I like Visual Studio. I wish VSCode could replace Visual Studio for my current work, but I don't think it works well with .NET Framework solutions yet (and may never will).

I find it's not as turn key as Visual Studio. It has a lot of the same, or even better and different functionality, but if I'm opening and new solution, 99/100 times if I want to run it immediately without tinkering it'll be in Visual Studio. I love code for the extensions, but Visual Studio still feels easier to get something up and running in.

I find the opposite to be true. We’ve been a C# shop for decades, but with python and JavaScript creeping in, we’re just so used to clis.

Visual Studio does a lot of things, but the truth is that we never use them. Well except for Linq-To-Sql which is ironically removed from the standard setup because Microsoft considers it bad practice. Five years ago we downgraded from Enterprise to Professional, exactly because what we do 95% of the time is to build from an empty project without using any of the bling. To be fair, some of the bling like GitHub and docker integration have gotten fairly good, but because they were so bad for so long we simply got used to using them outside of Visual Studio.

I suspect that in 5 years we’ll be going from Professional to Visual Studio Code. I hope so, but things like intellisense just isn’t there yet.

Re: Python in Visual Studio Code – April 2019 Release

#28

Post by galacticdessert »

MapleWalnut wrote: post #10

I’ve found the language server practically useless because of regressions introduced in later versions. This wouldn’t be too bad except the language server auto updates. For now I’ve switched to the default Jedi version which was been working reliably.

I had plenty of issues with the language server as well, especially very high memory consumption and CPU usage.

For now I will not move away from Jedi again.

Re: Python in Visual Studio Code – April 2019 Release

#29

Post by JaimeThompson »

smnrchrds wrote: post #8
leadingthenet wrote: post #5

Earlier quoted context omitted.

As an aside, you can easily do this with PyCharm. It even works with vagrant images.

This is true, but unfortunately only for the paid version.

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.

Re: Python in Visual Studio Code – April 2019 Release

#30

Post by localhost »

benjaminjackman wrote: post #26

Overall I really like this extension and especially its interactive programming / notebook features. I am a big fan of jupyter notebooks, and wrote my own version for Scala (it was more inspired by Mathematica since Juypter didn't exist yet) a long long time ago. However having all the output be in a dedicated window as this extension does, that allows for scrolling back in the order things were run rather than in th…

Thanks for taking the time to write down your thoughts! What are some of the use cases where you find the interactive window superior to Jupyter? Do you use Jupyter as a complement or a replacement to VS Code?

Sorry about the annoying behavior! Some of this is clearly our fault, and I've asked the team to come by and respond to this. I've also added this to the list of things to chat with the VS Code team about as well.

Disclaimer: I originally came up with the idea for the interactive window based on the design constraints of VS Code, but the team that is currently working on this deserves all the credit for building and extending the original idea.

Post reply on HN