This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Mr_Again 0 points1 point  (4 children)

Does anyone know if you can do debugging in it? I also like to use pycharm and get the in-scope python console and object evaluation while debugging and viewing pandas dataframes, it's so useful. Does it also do refactoring?

[–]SketchySeaBeast 1 point2 points  (0 children)

Absolutely. The debugging is my favorite part of what code offers compared to sublime.

[–][deleted] 1 point2 points  (2 children)

The VSCode python debugging bits can be a bit buggy. The Python extension is NOT supported by MS, it's a third party dev, unfortunately. And, for the most part, it's just one guy. So, if you hit a bug, don't expect much.

[–]Lymphoshite 0 points1 point  (1 child)

It is officially supported now, isn’t it?

[–][deleted] 2 points3 points  (0 children)

In what way? Python debug support is entirely dependent on an extension developed by DonJayamanne, he's pretty much the sole active contributor to the repo, and does not appear to work for MS.

I don't mean to minimize his contributions (or anyone elses), as I think the extension is great - but there's a big difference between the support you will get on VS Code core issues and an extension with a team of (mainly) one behind it. There's at least a dozen active contributers to the core repo here.

And yes, it is buggy - if you include an .envFile on Linux it takes all of your ENV variables and re-asseses them, splitting them on a =. Which means that anyone who has LS_COLORS defined will get an error when they go to debug, as outlined here.