Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Variable explorer doesn't work for Numpy arrays when Numpy is not installed #22784

Open
johnh865 opened this issue Oct 31, 2024 · 4 comments
Open

Comments

@johnh865
Copy link

Description

What steps will reproduce the problem?

When trying to open an array, or if I click a value of a numpy data type, an error pops up "Spyder was unable to retrieve the value of this variable from the console. The error message was:

An unknown error occurred. Check the console because its contents could have been printed there.

Note: please don't report this problem on Github, there's nothing to do about it.
"

Although the message claims there's nothing to do about it, I'm pretty sure for older versions of numpy, Spyder had no problem displaying those arrays.

Versions

  • Spyder version: 6.0.1 (pip)
  • Python version: 3.11.8 64-bit
  • Qt version: 5.15.2
  • PyQt5 version: 5.15.11
  • Operating System: Windows-10-10.0.19045-SP0

Dependencies

# Mandatory:
aiohttp >=3.9.3                  :  3.10.10 (OK)
asyncssh >=2.14.0,<3.0.0         :  2.17.0 (OK)
atomicwrites >=1.2.0             :  1.4.1 (OK)
chardet >=2.0.0                  :  5.2.0 (OK)
cloudpickle >=0.5.0              :  3.1.0 (OK)
cookiecutter >=1.6.0             :  2.6.0 (OK)
diff_match_patch >=20181111      :  20241021 (OK)
github >=2.3.0                   :  2.4.0 (OK)
importlib_metadata >=4.6.0       :  8.5.0 (OK)
intervaltree >=3.0.2             :  3.1.0 (OK)
IPython >=8.13.0,<9.0.0,!=8.17.1 :  8.29.0 (OK)
jedi >=0.17.2,<0.20.0            :  0.19.1 (OK)
jellyfish >=0.7                  :  1.1.0 (OK)
jsonschema >=3.2.0               :  4.23.0 (OK)
keyring >=17.0.0                 :  25.4.1 (OK)
nbconvert >=4.0                  :  7.16.4 (OK)
numpydoc >=0.6.0                 :  1.8.0 (OK)
parso >=0.7.0,<0.9.0             :  0.8.4 (OK)
pexpect >=4.4.0                  :  4.9.0 (OK)
pickleshare >=0.4                :  0.7.5 (OK)
psutil >=5.3                     :  6.1.0 (OK)
pygments >=2.0                   :  2.18.0 (OK)
pylint >=3.1,<4                  :  3.3.1 (OK)
pylint_venv >=3.0.2              :  3.0.3 (OK)
pyls_spyder >=0.4.0              :  0.4.0 (OK)
pylsp >=1.12.0,<1.13.0           :  1.12.0 (OK)
pylsp_black >=2.0.0,<3.0.0       :  2.0.0 (OK)
pyuca >=1.2                      :  1.2 (OK)
qdarkstyle >=3.2.0,<3.3.0        :  3.2.3 (OK)
qstylizer >=0.2.2                :  0.2.3 (OK)
qtawesome >=1.3.1,<1.4.0         :  1.3.1 (OK)
qtconsole >=5.6.0,<5.7.0         :  5.6.0 (OK)
qtpy >=2.4.0                     :  2.4.1 (OK)
rtree >=0.9.7                    :  1.3.0 (OK)
setuptools >=49.6.0              :  65.5.0 (OK)
sphinx >=0.6.6                   :  8.1.3 (OK)
spyder_kernels >=3.0.0,<3.1.0    :  3.0.0 (OK)
superqt >=0.6.2,<1.0.0           :  0.6.7 (OK)
textdistance >=4.2.0             :  4.6.2 (OK)
three_merge >=0.1.1              :  0.1.1 (OK)
watchdog >=0.10.3                :  5.0.3 (OK)
yarl >=1.9.4                     :  1.16.0 (OK)
zmq >=24.0.0                     :  26.2.0 (OK)

# Optional:
cython >=0.21                    :  None (NOK)
matplotlib >=3.0.0               :  None (NOK)
numpy >=1.7                      :  None (NOK)
pandas >=1.1.1                   :  None (NOK)
scipy >=0.17.0                   :  None (NOK)
sympy >=0.7.3                    :  None (NOK)
@dalthviz
Copy link
Member

dalthviz commented Nov 1, 2024

Hi @johnh865 thank you for the report! I think this could be related with #20671 Are you by any chance using a custom interpreter? One of the reasons this message could appear is if you are using a custom interpreter and the env from where Spyder was launched have incompatible versions of the package you are using or also if you don't have the package installed over the env Spyder was launched.

Let us know if the info above helps!

@dalthviz dalthviz self-assigned this Nov 1, 2024
@ccordoba12 ccordoba12 changed the title Variable explorer doesn't seem to work for numpy datatypes. Variable explorer doesn't seem to work for Numpy arrays Nov 4, 2024
@ccordoba12
Copy link
Member

The cause for this is very simple @johnh865: you don't have Numpy installed alongside Spyder, as can be seen in the list of dependencies you posted:

numpy >=1.7                      :  None (NOK)

And Spyder needs Numpy to manipulate and display arrays in the Variable Explorer. We list it as an optional dependency to not make installing Spyder too heavy.

However, the error message for this problem can be certainly improved and we'll try to do it in a later version.

@ccordoba12 ccordoba12 added this to the v6.0.4 milestone Nov 4, 2024
@ccordoba12 ccordoba12 changed the title Variable explorer doesn't seem to work for Numpy arrays Variable explorer doesn't work for Numpy arrays when Numpy is not installed Nov 4, 2024
@dalthviz dalthviz removed this from the v6.0.4 milestone Dec 12, 2024
@dalthviz
Copy link
Member

Closing as a duplicate of #20671

@dalthviz dalthviz closed this as not planned Won't fix, can't repro, duplicate, stale Dec 12, 2024
@dalthviz dalthviz reopened this Dec 23, 2024
@dalthviz dalthviz added this to the v6.1.0 milestone Dec 23, 2024
@dalthviz
Copy link
Member

dalthviz commented Dec 23, 2024

Reopening since improving numpy version detection to provide better messaging is possible:

  • Inform users numpy isn't installed (maybe possible for a bug fix release - e.g 6.0.4)
  • Inform users discrepancy between Spyder runtime and custom interpreter env versions detailing versions (needs changes over spyder-kernels so only possible for at least a minor release - e.g 6.1.0)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants