KeyError('pandas._libs.interval') while opening a dataframe in variable explorer in dmg version of spyder

Issue Report Checklist

• Searched the issues page for similar reports
• Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
• Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
• Could not reproduce inside jupyter qtconsole (if console-related)
• Tried basic troubleshooting (if a bug/error)
  • Restarted Spyder
  • Reset preferences with spyder --reset
  • Reinstalled the latest version of Anaconda
  • Tried the other applicable steps from the Troubleshooting Guide
• Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description

I’m getting KeyError(‘pandas._libs.interval’) while opening a dataframe in the variable explorer. I’m using dmg version of spyder on an anaconda environment. I reinstalled both anaconda and spyder but didn’t solve the issue.

What steps reproduce the problem?

What is the expected output? What do you see instead?

Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

• Spyder version: 4.2.1
• Python version: 3.8.5
• Qt version:
• PyQt version:
• Operating System name/version: macos 11.1

Dependencies

PASTE DEPENDENCIES HERE

[ccordoba12]

There’s a workaround. Please go to pull request https://github.com/spyder-ide/spyder/pull/14600, click on View details, then the Details link to the right of macOS App Bundle (Full), then Artifacts (to the right):

and finally click on Spyder.dmg on the menu that appears there.

That will give you an installer with our latest fixes in our stable branch (i.e. everything that will be part of 4.2.2, including our fix for Pandas). However, please be aware that it could contain other bugs or problems because it’s still a work in progress.

[mhdmyz]

The only question is wouldn’t it be better to provide us a dmg version for Spyder 4.2.2.dev instead of Spyder 4.3.0.dev0? I’m not sure whether it’s possible, I just think it would be safer considering the probable bugs!

Good thinking. However, that correspond to the way we name development versions. We don’t name bugfix releases (i.e. 4.2.2dev0), just minor ones (i.e. 4.3.0dev0).

I understand that’s a bit odd (specially because there’s not going to be a 4.3.0 release at the end), but we decided to do that years ago for all projects we maintain, so now it’s kind of hard for us to change it.

Got you! If it’s only a naming thing, it won’t be an issue. Again Thanks!