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

PR: Fix error when we can't detect Spyder in conda list output (Utils) #22156

Merged
merged 1 commit into from
Jun 11, 2024

Conversation

ccordoba12
Copy link
Member

Description of Changes

I really don't know when this situation could happen, i.e. Spyder installed in a conda env and yet not available in the output of conda list. But since it was reported by a user, we need to address it.

Issue(s) Resolved

Fixes #22054.

Affirmation

By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: @ccordoba12

@ccordoba12 ccordoba12 added this to the v5.5.5 milestone Jun 10, 2024
@ccordoba12 ccordoba12 self-assigned this Jun 10, 2024
@ccordoba12 ccordoba12 changed the base branch from master to 5.x June 10, 2024 15:45
mrclary added a commit to mrclary/spyder that referenced this pull request Jun 10, 2024
…spyder-ide/spyder/actions/runs/9451452145/job/26032800727?pr=22156)

Warning: 0 15:50:35,969 [WARNING] [traitlets] -> Kernel Provisioning: The 'local-provisioner' is not found.  This is likely due to the presence of multiple jupyter_client distributions and a previous distribution is being used as the source for entrypoints - which does not include 'local-provisioner'.  That distribution should be removed such that only the version-appropriate distribution remains (version >= 7).  Until then, a 'local-provisioner' entrypoint will be automatically constructed and used.
The candidate distribution locations are: []
2024-06-10 15:50:35,969 [DEBUG] [traitlets] -> Instantiating kernel 'Python 3 (Spyder)' with kernel provisioner: local-provisioner
Error: -10 15:50:35,969 [ERROR] [traitlets] -> 'module' object is not callable
Traceback (most recent call last):
  File "/Users/runner/work/spyder/spyder/dist/Spyder.app/Contents/Resources/lib/python3.10/jupyter_client/manager.py", line 87, in wrapper
  File "/Users/runner/work/spyder/spyder/dist/Spyder.app/Contents/Resources/lib/python3.10/jupyter_client/manager.py", line 435, in _async_start_kernel
  File "/Users/runner/work/spyder/spyder/dist/Spyder.app/Contents/Resources/lib/python3.10/jupyter_client/manager.py", line 395, in _async_pre_start_kernel
  File "/Users/runner/work/spyder/spyder/dist/Spyder.app/Contents/Resources/lib/python3.10/jupyter_client/provisioning/factory.py", line 101, in create_provisioner_instance
TypeError: 'module' object is not callable

I suspect an issue with jupyter_client since the last successful workflow on 5.x branch had 8.6.1 and this failing one has 8.6.2. traitlets is 5.14.3 in both workflows.

Let's see if this works.
mrclary added a commit to mrclary/spyder that referenced this pull request Jun 10, 2024
@ccordoba12 ccordoba12 merged commit cbb94d1 into spyder-ide:5.x Jun 11, 2024
23 checks passed
@ccordoba12 ccordoba12 deleted the issue-22054 branch June 11, 2024 16:36
ccordoba12 added a commit that referenced this pull request Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

local variable 'channel_url' referenced before assignment error when checking for updates
1 participant