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 encountered a problem when opening numpy array

See original GitHub issue

Description

What steps will reproduce the problem?

build 120x12 array of float64

double click to open in variable explorer

Traceback

  File "C:\Users\CZ3QFP\miniconda2\envs\gmrpg_dev\lib\site-packages\spyder\widgets\variableexplorer\collectionseditor.py", line 482, in createEditor
    if not editor.setup_and_check(value, title=key, readonly=readonly):
  File "C:\Users\CZ3QFP\miniconda2\envs\gmrpg_dev\lib\site-packages\spyder\widgets\variableexplorer\arrayeditor.py", line 620, in setup_and_check
    self.data.flags.writeable = True
ValueError: cannot set WRITEABLE flag to True of this array

Versions

Spyder version: 3.3.2
Python version: 3.7.2
Qt version: 5.9.6
PyQt5 version: 5.9.2
Operating System: Windows 10

Dependencies

pyflakes >=0.6.0  :  2.0.0 (OK)
pycodestyle >=2.3 :  2.4.0 (OK)
pygments >=2.0    :  2.3.1 (OK)
sphinx >=0.6.6    :  1.8.2 (OK)
rope >=0.9.4      :  0.11.0 (OK)
jedi >=0.9.0      :  0.13.2 (OK)
nbconvert >=4.0   :  5.3.1 (OK)
pandas >=0.13.1   :  None (NOK)
numpy >=1.7       :  1.16.0rc2 (OK)
sympy >=0.7.3     :  None (NOK)
cython >=0.21     :  None (NOK)
qtconsole >=4.2.0 :  4.4.3 (OK)
IPython >=4.0     :  7.2.0 (OK)
matplotlib >=2.0.0:  3.0.2 (OK)
pylint >=0.25     :  2.2.2 (OK)

Issue Analytics

State:
Created 5 years ago
Comments:21 (11 by maintainers)

Top GitHub Comments

1reaction

CAM-Gerlachcommented, Apr 20, 2019

@NaderNazemi Yes, as you can see by the fact that it is closed, it is marked with the milestone of a released Spyder version (3.3.3) and is addressed in the linked PR, #8632 .

0reactions

CAM-Gerlachcommented, Nov 27, 2020

@Li-Shu14 Hey, Spyder 3.3.3 is almost two years old and is no longer supported, the current version being 4.2.0. Can you verify if this problem still occurs with 4.2.0 and a supported release of Numpy 1.16+? Thanks.