Like sure, I could drop into pdb and tediously work through printing things out (and good luck if you are printing out ndarrays or large dictionaries or wanting to look through instance variables for an instance in your local execution context) and take 4X longer to figure out why something isn't working, or just in a quick glance figure out exactly what the issue is. I guess I'll continue being a n00b developer happily relying on a variable explorer whenever available :o).
This is critical for scientific computing because you're constantly interacting with data (i.e. reading, cleaning, plotting and analyzing it), so having a dedicated pane for it is a great advantage.
Anyone who's dealt with huge data arrays appreciate it.
Also, just wanna say Spyder looks like it's come a long way in the last decade. Congrats on some fine work!
Spyder got me off Matlab nearly a decade ago. I had just learned Python and had trouble getting Matlab access in my lab (I was an undergrad working on radio astro data) and after many weeks fighting with our dept. IT over a license, I started using Spyder, and it was pretty awesome. So many thanks to everyone who worked on Spyder!
Oh yeah, this is so true! Ten years ago, when I joined the project, it was just Pierre (Spyder's original author) and me. Then, in 2016, Anaconda gave us the resources to hire three developers part-time to work on the project, which was a huge boost (between 2012 and 2016 it was mostly me and three or four volunteers).
Now we have a team of five people working part or full time on Spyder, all hired by Quansight: https://www.quansight.com/
So you can expect lots more good things to come in the future.
Maybe you could let Quansight know their homepage is a bit broken (at least on Firefox on Android): The "READ MORE" link shows up on top of the text.
>Eh, Streamlit and PyCharm is a much more powerful combination IMO.
What is you PyCharm + Streamlit use case and workflow? Just curious because I have just learned about Streamlit from your comment.
Okay, so maybe a variable viewer isn’t a bad thing. I just know from personal experience that people get in the habit of scrolling through large arrays, instead of learning numpy’s slicing and shape concepts, or functions that detect e.g. the index of NaNs... I think that was mainly my point.