-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Python autocompletion doesn't work with VS Code Python extenstion (Pylance) #892
Comments
I think I kinda figured it out. When I install the Python Extension it installs another extension along with it called Pylance. And that is the one that is causing this problem. When I disable Pylance the autocompletion works. I have to test it out on the original VS Code as well to know if it is a problem of Pylance or VSCodium. And if the problem is with Pylance [Hopefully] I will close this Issue |
I tested Pylance on the original VS Code and VSCodium and it seems like the problem exists only on the latter. I don't know if this is a problem only for me or anyone else. So if someone else tested it out and comment their observations it might be helpful. PS: To be honest, I don't mind using the Python Extension only (ie without Pylance). |
@an4s911 confirmed here as well with version 1.61. It seems to me that the last working release is the 1.56 |
The issue is that Microsoft prevents PyLance from being used in non-official builds. Source: https://www.reddit.com/r/linux/comments/k0s8qw/comment/ggnqes7/ |
@SebastianGrans thanks for sharing but still I don't get the extension working. I've changed the |
@ghtmtt What does it say in the Python output terminal? Before I change
After I change, it simply prints:
with no error after it. |
if you mean running a file in the python terminal I can do it without any problem. I just have issues with the autocompletion |
@ghtmtt No. What I mean is the output from the Python extension. You can see its output by opening a terminal inside Codium, and then go to the output tab, and select Python. See the screenshot below. |
This is what I have
|
I've disable most of the extensions but still nothing. No external API and not standard autocomplete |
I have the same issue on Windows 10, VsCodium 1.61.2 I originally was not getting even classes and functions in the outline so I removed Pylance, which helped with the Outline but I now have no autocompletion. This use work fine in early versions this year but I cant tell the last working version. |
Thank you, it worked for me too. 👍 |
I've already tried this solution but it never worked for me. BUT it seems that the combination of 2 different changes in the {
"nameShort": "Visual Studio Code",
"nameLong": "Visual Studio Code",
...
...
"extensionsGallery": {
"serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
"cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
"itemUrl": "https://marketplace.visualstudio.com/items"
}, |
where is "product.json" located? |
Found it, need to edit file |
The python extension is tricky since it's using a closed source server (pylance). |
Use the jedi language server instead of pylance. |
Thanks. Just like some others have mentioned, this worked for me as well. I think I will close the issue now as the issue is solved for me as well as others. If the above mentioned solution didn't work then try the below and it should probably fix it.
And I am closing this Issue. Thanks to everyone who helped and contributed ✌ |
Sorry for issue necromancy, but I found another potential solution today: |
@asdorsey Thanks. I will check it out |
Describe the bug
When I am using VS Codium and have the VS Code Python and Pylance extensions installed and enabled, I don't get any autocomplete options or suggestions and it shows
No suggestions
.As you can see I have enabled only the Python extension and it shows
No suggestions
. Now when I disable I get some suggestions but they are not Python suggestions, but rather just suggesting text from other parts of the file.But not even this works when the extension is turned on.
Please confirm that this problem is VSCodium-specific
Please confirm that the issue/resolution isn't already documented
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: