The VS code details I am using are -
Version: 1.47.2 (user setup)
Commit: 17299e413d5590b14ab0340ea477cdd86ff13daf
Date: 2020-07-15T18:22:06.216Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.14393
The python extension version used is v2020.7.94776
Unfortunately I don't know what triggered this. So I am attaching output log for python extension. I see multiple traceback there but can't guess whats wrong.
python_extension_output_log.txt
My python configuration looks like -
"python.defaultInterpreterPath": "C:/Anaconda3/python.exe"
"python.formatting.autopep8Path": "C:/Anaconda3/Scripts/autopep8.exe",
"python.formatting.provider": "autopep8",
"python.formatting.autopep8Args": [
"--ignore",
"E302"
],
"python.autoComplete.extraPaths": [
"
],
"python.linting.pylintArgs":` [
"--disable=invalid-name",
"--init-hook",
"import sys; sys.path.append('
]
Are you using jedi or Microsoft (language server)? See what you have for "python.languageServer" setting.
We have recently released a new and more performant language server called Pylance.  You can download Pylance from the marketplace and install it alongside the core Python extension. Because our team's development efforts have shifted to support the new language server, we'd encourage you to try it out. If you try out Pylance and this issue persists, you can open an issue on the pylance-release repo.
As part of trying various things I tried both Jedi and Microsoft. Both
language servers didn't work. Right now I don't have any language server
specified so probably it's using default. I will try pylance and let you
know. Thank you for your quick response.
On Thu, Jul 23, 2020, 3:30 AM Karthik Nadig notifications@github.com
wrote:
Are you using jedi or Microsoft (language server)? See what you have for
"python.languageServer" setting.We have recently released a new and more performant language server called
Pylance. You can download Pylance
https://devblogs.microsoft.com/python/announcing-pylance-fast-feature-rich-language-support-for-python-in-visual-studio-code/ from
the marketplace
https://marketplace.visualstudio.com/items?itemName=ms-python.vscode-pylance and
install it alongside the core Python extension. Because our team's
development efforts have shifted to support the new language server, we'd
encourage you to try it out. If you try out Pylance and this issue
persists, you can open an issue on the pylance-release repo
https://github.com/microsoft/pylance-release.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-python/issues/13104#issuecomment-662860203,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2OLFMS4D3RJUCOPVLIED3R47RKZANCNFSM4PFD6JVQ
.
I tried Pylance. I had to modify python.autoComplete.extraPaths to python.analysis.extraPaths. It took some to figure out ${workspaceFolder} isn't supported. But once that is done its working well. I will explore it further but looks very promising. Thank you!! for your help.
same over here, after auto updated the vs code, the autocomplete doesn't work.
@yongen9696 Try and use Pylance. As i mentioned in me previous comments, we are switching over the efforts to pylance.
@yongen9696 Try and use Pylance. As i mentioned in me previous comments, we are switching over the efforts to
pylance.
tried pylance, doesn't work as well in autocomplete bracket
@yongen9696 Please file an issue on pylance, https://github.com/microsoft/pylance-release .
Closing this since the original issue is addressed with using pylance.
Most helpful comment
Are you using
jediorMicrosoft(language server)? See what you have for"python.languageServer"setting.We have recently released a new and more performant language server called Pylance.  You can download Pylance from the marketplace and install it alongside the core Python extension. Because our team's development efforts have shifted to support the new language server, we'd encourage you to try it out. If you try out Pylance and this issue persists, you can open an issue on the pylance-release repo.