Skip to content

Python jedi intellisense extension issue #10836

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
jessesnyder opened this issue Mar 27, 2020 · 9 comments
Closed

Python jedi intellisense extension issue #10836

jessesnyder opened this issue Mar 27, 2020 · 9 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@jessesnyder
Copy link

Autocompletion not working at all, before and after today's update.

CPU-20200327T195644.869Z.cpuprofile.txt

  • Issue Type: Bug
  • Extension Name: python
  • Extension Version: 2020.3.69010
  • OS Version: Darwin x64 17.7.0
  • VSCode version: 1.43.2
{
	"messages": [],
	"activationTimes": {
		"codeLoadingTime": 873,
		"activateCallTime": 71,
		"activateResolvedTime": 241,
		"activationReason": {
			"startup": false,
			"extensionId": {
				"value": "ms-python.python",
				"_lower": "ms-python.python"
			},
			"activationEvent": "onLanguage:python"
		}
	},
	"runtimeErrors": []
}
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Mar 27, 2020
@CatNofishing
Copy link

I have the same problem, jedi is stuck on ' pyi' file , and It will last a long time.

@karthiknadig karthiknadig self-assigned this Mar 30, 2020
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Mar 30, 2020
@karthiknadig karthiknadig added the bug Issue identified by VS Code Team member as probable bug label Mar 30, 2020
@CatNofishing
Copy link

CatNofishing commented Mar 31, 2020

77847746-ff26a080-71f1-11ea-9d64-a5a0296c8123
When you open the pyi file, jedi will stuck on loading.

@karthiknadig
Copy link
Member

@jessesnyder Are you using Language Server or Jedi? You can look for the jediEnabled setting and see if it is set.

@1470391328 That looks like a different issue. Please try using Language Server and see if it helps with this.

@CatNofishing
Copy link

CatNofishing commented Apr 2, 2020

😂 Language Server does not support PYI and it has many bugs. I like to use Jedi

@karthiknadig
Copy link
Member

@1470391328 I see that you filed microsoft/python-language-server#1978 on MPLS. You don't mention that you are using LS or jedi there. From the GIF you shared it looks like you are using Jedi. I also know that David asked you to file this here ( based on comments here davidhalter/jedi#1534), if this is an issue with how extension is using jedi then addressing this will have to wait until we get to updating the extension to use new jedi APIs.

At the moment the option is to try MPLS. MPLS uses *.pyi files to show completion for some standard library files (see here https://github.com/microsoft/python-language-server/tree/master/src/Analysis/Ast/Impl/Typeshed/stdlib/2and3). If you believe this is not working please file a issue on MPLS about PYI.

/cc @jakebailey

@jakebailey
Copy link
Member

jakebailey commented Apr 2, 2020

If this is MPLS, then this is expected behavior outside of user code; we don't support editor features in library code to not use too much memory (but this can be changed via my comment at: microsoft/python-language-server#840 (comment))

But I can't really tell which is being used. MPLS definitely supports pyi files.

@CatNofishing
Copy link

@karthiknadig @jakebailey Thank you for your reply. My English is poor. I have to use Google translation to submit issues. Please don't mind my grammar , my description may not be clear.

@CatNofishing
Copy link

#11009

@karthiknadig
Copy link
Member

This should be addressed by #10895

@ghost ghost removed the triage label May 13, 2020
@lock lock bot locked as resolved and limited conversation to collaborators May 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

4 participants