Skip to content

Switching to JEDI returns one-time error #19014

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

Closed
sbatten opened this issue Apr 26, 2022 · 2 comments
Closed

Switching to JEDI returns one-time error #19014

sbatten opened this issue Apr 26, 2022 · 2 comments
Assignees
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug

Comments

@sbatten
Copy link
Member

sbatten commented Apr 26, 2022

Testing #18964

image
image

Context: Using remote repo to open in web

  1. Switch Python Language Server from Pylance to Jedi
  2. Try to trigger intellisense
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Apr 26, 2022
@karthiknadig karthiknadig added bug Issue identified by VS Code Team member as probable bug area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. triage and removed triage-needed Needs assignment to the proper sub-team labels Apr 27, 2022
@kimadeline
Copy link

Related: #19015

@kimadeline
Copy link

Ok so turns out we don't support Jedi on web, only Pylance (with partial Intellisense).

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

3 participants