Spyder-Like variable explorer

[YashKarthik]

Feature: Variable explorer

The variable explorer in the notebooks is a important part of many data science IDEs, though vscode is not a full blown IDE I prefer it over others, its amazing. Vscode has a amazing features, just that the variable explorer doesn't feel/look so good, an explorer like in spyder or even Pycharm would be a nice feature and I'm sure many ppl would like that interface.
Thanks

[DavidKutu]

Thanks for your feedback @YashKarthik. We'll discuss this feature in our next triage.

[YashKarthik]

👍🏻👍🏻 @DavidKutu

[YashKarthik]

@greazer , the variable explorer in the vscode Jupiter notebooks cover a lot of vertical space, whereas it'll be more convenient if it were on part the activity bar and have a squarish panel when opened. Also a data frame viewer like one in Jupyterlab would also be a nice feature.

[jasonboh]

Spyder has the very useful ability of viewing all kind of Python objects in the Variable Explorer. Currently, VS Code's Variable Explorer is very limited compared to the type of objects one can view in Spyder. For example, if I create Python class and then create a variable that stores an instance of that class, the Spyder variable explorer lets me double click on the instance variable and see all attributes. And I can keep descending into the hierarchy by double clicking. For example, if an attribute stores a list, I can double click on the attribute and view all element of the list. If the attribute is a nametuple or dict or set some other built-in Python object, I can double click on it and it open the view of that object. You can also actually edit values within a list, or dict
or whatever and then interact with the edited values in the kernel. My understanding is that MATLAB behaves similarly (I don't know from personal experience). But the variable Explorer is one of the most-loved features in Spyder, so adding similar capabilities to VS Code would be great!

[jontis]

Yes! Though VS Code has come a long way, the variable explorer is still the reason I chose Spyder every time for Data Science tasks.

[jasonboh]

Me too. I find VS Code's current Variable Explorer is of super-limited use to me. However, VS Code offers so many other great features that Spyder does not. So, if VS Code could just close this one huge gap, it would be fantastic.

[bibinvargheset]

Me too. I find VS Code's current Variable Explorer is of super-limited use to me. However, VS Code offers so many other great features that Spyder does not. So, if VS Code could just close this one huge gap, it would be fantastic.

The above comments are very relevant and the redirected issue is closed. The variable explorer is needed for both the python interactive window as well as the normal python window.

Py charm has a good variable explorer and Virtual environment set up.

[Ikhwansong]

I agree with them. So please improve the 'variable explorer'

[NikilXYZ]

I agree - this is especially useful for matrices and csv / table type data.
The one reason I use spyder (if I'm using Python) or use R studio (if I'm using R) instead of VS Code for scientific computing, data science, or image processing.

[johan-lorentzon]

I agree, I'd love to be able to use VS Code for scientific python since it's far superior to Spyder in other aspects but a working variable explorer and data viewer is an absolute requirement for a scientific IDE. The current VS Code one has too limited capabilities and also is far too slow to be useful.

[jasonboh]

@DonJayamanne @DavidKutu Hi guys, just to expand upon the request.... It would be great if the focus wasn't only on "data viewing". yes, that's important, but a more general, all-purpose variable viewer would be useful, where users could see all attributes and methods of each object alive in the kernel. This is what Spyder offers. It's not just a viewer for data objects.... it's a viewer for ALL variables, not matter their type. I believe that Spyder pickles objects in order to view their attrs and methods in the Variable Explorer. You can double click on any object and keep descending into the hierarchy of the objects inside of them. And, regarding data viewing, currently complex numbers are not supported in the Data Viewer. This is a requirement for my field of engineering.

[NikilXYZ]

Yep I agree with this. Also make it so the viewer refreshes the values on any update to the variable. Currently in VS Code I have to keep opening a new tab every time the values change

…

On Sat, May 8, 2021, 9:21 AM jbiz25 ***@***.***> wrote: @DonJayamanne <https://github.com/DonJayamanne> @DavidKutu <https://github.com/DavidKutu> Hi guys, just to expand upon the request.... It would be great if the focus wasn't only on "data viewing". yes, that's important, but a more general, all-purpose variable viewer would be useful, where users could see all attributes and methods of each object alive in the kernel. This is what Spyder offers. It's not just a viewer for data objects.... it's a viewer for ALL variables, not matter their type. I believe that Spyder pickles objects in order to view their attrs and methods in the Variable Explorer. You can double click on any object and keep descending into the hierarchy of the objects inside of them. And, regarding data viewing, currently complex numbers are not supported in the Data Viewer. This is a requirement for my field of engineering. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1148 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APW66EN2SK7P7GY2OS4XEX3TMVCGNANCNFSM4TVCLQNA> .

[DonJayamanne]

What you're after is mentioned here:#5532

• Variable explorer for all data types, dictionary, plots, widgets, pickle objects, etc.
• and then bring able to explore each variable (expanding ducts/pickled objects, opening plots in separate windows, opening widgets in a separate windows)

@jbiz25, @NikilXYZ
Please upvote #5532 that issue if that's what you're after

[jasonboh]

That's exactly it. Will upvote. Thanks @DonJayamanne

[mho21]

Thank you for picking up! as this drawback of vscode is the only reason I still use intellij right now, upvote both issue! #5532

[kickbone]

Could not agree more. Looking forward to an upgraded variable explorer in VS Code!

[IsaiahvH]

As far as I know, the current variable explorer also does not offer a way to search for a variable by name.
When there is many variables, scrolling in a small window becomes tedious and it would be great if this feature would also be considered.

[Y-H-Joe]

another vote here!

[Aizenz]

Vote for a better variable explorer too.
The color indicating the size of variable is really helpful!

[ldorigo]

+1. Also, I'm wondering if you couldn't "just" re-use the variable viewer that is used in the debugger? I find it 10x better in terms of interactivity than the current "JUPYTER: VARIABLES" pane.

[JOPEDSAN]

I agree with everything that is said in the issue. The reason why I don't definitely switch from Spyder to VS Code is the variable browser. I think it is essential when creating a structure to be able to visualize it and navigate with a double-click (example: dictionary of dictionaries, etc...). I hope that this improvement in the visualization of variables will be added, as soon as it will be solved it will be the definitive tool.
Thanks !!!

[dkumbhani411]

I reached out to these comments through google from same but I can not get an answer.
Is there any update coming regarding that?

[KangOxford]

Please add a variable explorer!

[DonJayamanne]

More suggestions from here #11679

• showing a dataframe is fast
• it is opened in its own window that you can enlarge at will
• all columns are much wider and they can be even resized automatically

[Cglezf]

Please add a variable browser!!!

[mateuszrenno]

I agree! Spyder variable explorer is the best.

[jmew]

Just wanted to share this extension from Microsoft that integrates with Notebooks in VS Code, to allow you to open any Pandas DataFrame in an interactive data wrangler

https://marketplace.visualstudio.com/items?itemName=ms-toolsai.datawrangler

[Cglezf]

That not resolve the inspector variables (Spyder-like) for object. Sometimes we need to explore the variables within the objects.

[starball5]

What's the relationship between this issue ticket and the work being done with microsoft/vscode#165445?

[BENSONCHIEN]

After almost 4 years, another vote here!

Because vscode github copliot and Spyder variable explorer..., I keep switching between the two IDEs.

[amunger]

you can try out the experimental built-in variable view with "notebook.experimental.variablesView": true - A "Notebook Variables" section should show up in the run/debug sidebar when a python kernel from the jupyter extension is running. It still needs some polish, but should be closer to what is asked for here.

[wrgrant]

Nice @amunger !!
This is a great start and covers everything I need for script development.

[NikilXYZ]

Does this only work for notebook files? *NIKIL RAGAV** | **CEO | **inventXYZ * alum of Wharton Business | Penn Electrical Engineering 832.910.9645 | inventXYZ.com <http://www.inventxyz.com/> Integrating hands-on real-world STEM & CS experiences into every core middle & high school course

…

On Mon, Jul 1, 2024 at 2:43 PM William Grant ***@***.***> wrote: Nice @amunger <https://github.com/amunger> !! This is a great start and covers everything I need for script development. — Reply to this email directly, view it on GitHub <#1148 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APW66EMDNEMFZD6JBOWORWLZKHEORAVCNFSM4TVCLQNKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMRQGEYTEMRSHE3A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[WhiteRavenTechnology]

you can try out the experimental built-in variable view with "notebook.experimental.variablesView": true - A "Notebook Variables" section should show up in the run/debug sidebar when a python kernel from the jupyter extension is running. It still needs some polish, but should be closer to what is asked for here.

Well I thought this was gonna be it. Can't view dataframes in any kind of dataviewer, and apparently when a variable becomes sufficiently complex (dictionary with nested dataframes), the "Notebook Variables" section just empties itself and stops working. Can't figure out what it is about my specific code that's causing it. The "Jupyter" variables tab is more useful than this since it at least doesn't empty itself.

Interestingly, when debugging, the normal variable viewer DOES work fine and allow me to dig into my dictionary objects and view dataframes in a data viewer from there (of course it says the dataviewer is going to be deprecated in favor of DataWrangler because why would we want something native that works instead of a bloated extension that doesn't).

I just want to be able to expand my dictionaries and view the dataframes contained on them. PyCharm does it. Spyder apparently does it. VS Code ALMOST does it perfectly when debugging.

This is nuts.

[amunger]

@WhiteRavenTechnology - the bug you mentioned with the dictionary object would is the kind of thing that we want to find while the feature is still experimental, so if you have a repro object, let us konw.

And DataWrangler's data viewer should be hooked up to the new variable explorer soon.

[BrazilForever11]

How can I try notebook.experimental.variablesView? I pasted it into search bar, but nothing came back.

[BrazilForever11]

I managed to get it work notebook.experimental.variablesView with Data Wrangler extension. I guess here is the bug tracker: #15141

This seems to work in notebook. Would it be possible to have it in flat python file?