question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Spyder 3 can't inspect values through the variable explorer while debugging

See original GitHub issue

When I debug a script using IPython console in spyder 3.0.0, I can see my variables listed in the variable explorer but when I try to inspect any variable there is an error message pops up. I think inspecting variables (especially DataFrame) while debugging was doable in spyder 2.3.8. I also tried debugging in Python console and there was no error message and I can check (double click) any variable through the variable explorer.

What steps will reproduce the problem? The attached screenshot shows my script file and the error message.

Please provide any additional information below screenshot

Versions and main components

  • Spyder Version: 3.0.0
  • Python Version: 2.7.11
  • Operating system: Win 8

Dependencies

Please go to the menu entry Help > Optional Dependencies (or Help > Dependencies), press the button Copy to clipboard and paste the contents below: jedi >=0.8.1 : 0.9.0 (OK) matplotlib >=1.0 : 1.5.1 (OK) nbconvert >=4.0 : 4.2.0 (OK) numpy >=1.7 : 1.10.4 (OK) pandas >=0.13.1 : 0.18.0 (OK) pep8 >=0.6 : 1.7.0 (OK) pyflakes >=0.5.0 : 1.3.0 (OK) pygments >=2.0 : 2.1.3 (OK) pylint >=0.25 : 1.5.4 (OK) qtconsole >=4.2.0: 4.2.1 (OK) rope >=0.9.4 : 0.10.3 (OK) sphinx >=0.6.6 : 1.4.8 (OK) sympy >=0.7.3 : 1.0 (OK)

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:26 (9 by maintainers)

github_iconTop GitHub Comments

4reactions
gilgtccommented, Jan 14, 2017

I completely agree with @AndyCash1. Sure it is always a good idea to fix issues but not at the expense of removing one of the most important tools for debugging.

3reactions
AndyCash1commented, Nov 21, 2016

I understand this question has been answered, but this issue is a show stopper for me. The ability to easily inspect and visualize variables like dictionaries and dataframes while debugging is the main reason why I use the Spyder IDE over others. Thus, I will continue to use Spyder 2.3.9 for now.

I would be curious to understand the logic behind this decision, and what the timeframe for it’s implementation in Spyder 3.X is. Thank you.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Spyder 3 can't inspect values through the variable explorer while ...
I think inspecting variables (especially DataFrame) while debugging was doable in spyder 2.3.8. I also tried debugging in Python console and there was...
Read more >
Spyder does not show class instance variables in variable ...
While debugging my python code using pdb in spyder, the IDE does not show the class instance variable in Variable Explorer. It's getting ......
Read more >
Variable Explorer — Spyder 5 documentation
The Variable Explorer gives you information on the name, size, type and value of each object. To modify a scalar variable, like an...
Read more >
Task | Software Design and Implementation
The debugger console: Most debuggers gives you a list of all the variables that are defined and have value in the program. Of...
Read more >
Examine suspended program | PyCharm Documentation
Right-click a variable on the Variables tab and select Set Value, or select the variable and press F2 . Enter the value for...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found