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

TypeError: string indices must be integers, not 'str' #22007

Closed
ppjerry opened this issue Apr 18, 2024 · 2 comments · Fixed by #21997
Closed

TypeError: string indices must be integers, not 'str' #22007

ppjerry opened this issue Apr 18, 2024 · 2 comments · Fixed by #21997

Comments

@ppjerry
Copy link

ppjerry commented Apr 18, 2024

Description

What steps will reproduce the problem?

TypeError: string indices must be integers, not 'str'

Traceback

Traceback (most recent call last):
  File "C:\Users\physics\anaconda3\envs\spyder-env\Lib\site-packages\spyder\workers\updates.py", line 119, in start
    channel, channel_url = get_spyder_conda_channel()
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\physics\anaconda3\envs\spyder-env\Lib\site-packages\spyder\utils\conda.py", line 232, in get_spyder_conda_channel
    if package_info["name"] == 'spyder':
       ~~~~~~~~~~~~^^^^^^^^
TypeError: string indices must be integers, not 'str'

Versions

  • Spyder version: 5.5.4 (conda)
  • Python version: 3.12.3 64-bit
  • Qt version: 5.15.8
  • PyQt5 version: 5.15.9
  • Operating System: Windows-10-10.0.19045-SP0

Dependencies

# Mandatory:
atomicwrites >=1.2.0             :  1.4.1 (OK)
chardet >=2.0.0                  :  5.2.0 (OK)
cloudpickle >=0.5.0              :  3.0.0 (OK)
cookiecutter >=1.6.0             :  2.6.0 (OK)
diff_match_patch >=20181111      :  20230430 (OK)
intervaltree >=3.0.2             :  3.1.0 (OK)
IPython >=8.13.0,<9.0.0,!=8.17.1 :  8.22.2 (OK)
jedi >=0.17.2,<0.20.0            :  0.19.1 (OK)
jellyfish >=0.7                  :  1.0.3 (OK)
jsonschema >=3.2.0               :  4.21.1 (OK)
keyring >=17.0.0                 :  25.1.0 (OK)
nbconvert >=4.0                  :  7.16.3 (OK)
numpydoc >=0.6.0                 :  1.7.0 (OK)
paramiko >=2.4.0                 :  3.4.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                     :  5.9.8 (OK)
pygments >=2.0                   :  2.17.2 (OK)
pylint >=3.1,<4                  :  3.1.0 (OK)
pylint_venv >=3.0.2              :  3.0.3 (OK)
pyls_spyder >=0.4.0              :  0.4.0 (OK)
pylsp >=1.11.0,<1.12.0           :  1.11.0 (OK)
pylsp_black >=2.0.0,<3.0.0       :  2.0.0 (OK)
qdarkstyle >=3.2.0,<3.3.0        :  3.2.3 (OK)
qstylizer >=0.2.2                :  0.2.2 (OK)
qtawesome >=1.3.1,<1.4.0         :  1.3.1 (OK)
qtconsole >=5.5.1,<5.6.0         :  5.5.1 (OK)
qtpy >=2.1.0                     :  2.4.1 (OK)
rtree >=0.9.7                    :  1.2.0 (OK)
setuptools >=49.6.0              :  69.5.1 (OK)
sphinx >=0.6.6                   :  7.2.6 (OK)
spyder_kernels >=2.5.1,<2.6.0    :  2.5.1 (OK)
textdistance >=4.2.0             :  4.5.0 (OK)
three_merge >=0.1.1              :  0.1.1 (OK)
watchdog >=0.10.3                :  4.0.0 (OK)
zmq >=24.0.0                     :  26.0.0 (OK)

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

Hi @ppjerry thank you for the feedback! I was unable to reproduce this but could you check what is the output of running something like:

conda list spyder --json --prefix <path of the env you are launching Spyder from>

Maybe this could be caused due to using some specific version of conda that changes the expected structure of the command output used inside the get_spyder_conda_channel function @ccordoba12 ?

@ccordoba12
Copy link
Member

This will be fixed by PR #21997 (the exact same error was reported there) and included in our next version (5.5.5), to be released shortly.

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

Successfully merging a pull request may close this issue.

3 participants