-
Notifications
You must be signed in to change notification settings - Fork 770
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
Pylance v2023.10.50 is incompatible with Python Extension v2020.8.109390 #5019
Comments
Same issue, Have to roll back to v2023.10.40 |
Same issue 👆 |
Just received the same message! |
Same. Broken. |
I have seemingly this problem too, on first glance, but I have a nuance to add: Also using the latest python extension did not fix the problem. I only tested with python interpreters already on my machine, here are the details: python 3.9.12 did not work, 3.10.4 did. It might have something to do with the various packages installed in each environment (I'm using conda to handle my vironements), but since I found a fix, I did not push the investigation forward. Hope it helped ! Note: I edited out the following text from my answer because after more testing I realized it was untrue: downgrading it to 2023.10.40 indeed worked.
|
Same issue for me, It works if I roll back to v2023.10.40, as suggested here. |
Not eve 10.40 works. It's all broken. |
I am using Python v2022.8.0 extension and Python 3.16.15 in devcontainer. My devcontainer: PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" Python Language Server log: [Info - 12:49:48 PM] (1752) Pylance language server 2023.10.50 (pyright cfe56bfb) starting Python extention log: Telemetry level is off
code: 127,
[ DAP Server launched with command: /workspaces/eta-regulator-board/web-api/.venv/bin/python3 /home/vscode/.vscode-server/extensions/ms-python.python-2022.8.0/pythonFiles/lib/python/debugpy/adapter |
Absolutely perfectly it was helped to me downgrading to Pylance 2023.10.40 version. This is very good Pylance to me |
Rolling Pylance language server back to 2023.10.40 solved this for me. 99% of you probably know this already, but I had to muck around Google to figure out how to roll back to previous version, so if anyone needs it, here's the quick how to:
|
Hey everyone. Unfortunately it's not feasible for us to maintain Pylance compatible with older versions of the Python extension. However, if the main reason why you're using an old version of the Python extension is support for debugging Python 2.7 or Python 3.5/3.6, there may be a better workaround so you can keep using the latest Pylance and Python extensions. We have a new Python Debugger extension that we are shipping separately so people can keep using the latest versions of the Python extension while having support for debugging older versions of Python. Specifically, the Python Debugger extension versions This way you can continue updating the Pylance and Python extensions and only use this one older version of the Python Debugger extension. |
I have similar problem with |
Same here with latest extension on Python (v2023.18.0) and Pylance (v2023.10.50). Changing to previous Pylance (v2023.10.40) worked for me aswell) Error: |
I am working with Python 3.10 and it's still giving me the same error rolling back to a previous version fixed it. |
The issue is happening even when using the latest versions of both Pylance and Python extensions. |
For everybody that's reproing the issue, can you state:
Thanks. We can't seem to reproduce it in house. Note: This error is expected if you're not actually using VS code (like VS codium or Cursor). It is NOT expected if you're using VS code through SSH/WSL/Dev Container. Those should work. |
This issue started today for me too. Python 3.10.13 via pyenv. Was doing other stuff, issues started after I just started using VSCode's variant of jupyter notebooks today. |
MacOS Sonoma 14.0 Local workspace. Virtual Python environment. Using JupyterNotebooks. Rolling back to Pylance v2023.10.40 seems to have fixed the problem. Issue happened in general use, switching between notebooks, scrolling. I haven't been actively executing code all that often. |
Can you try 2023.10.53? I wonder if it's related to this issue: microsoft/vscode#196740. Our best guess on the other issue is that the crashes in the Pylance server are starving the VS code extension host, preventing other things from working. It might be preventing the new message we added that verifies we're running inside of VS code. |
If you see this in the Debug Failure. Unable to find notebook URI for vscode-notebook-cell: 2023.10.53 might be the fix for the problem. It fixed that error. |
Sorry @csf90-uk what's your Python extension version? You listed your Python version, but the Python extension needs to be a certain version for Pylance to work too. |
Vs Code version: 1.83.1 |
VS Code Version: 1.83.1 Since my problem mainly happened during use of notebook, Jupyter extension version: v2023.9.1102792234. This could purely depend on the workload at the time is mainly using notebook. The symptoms for me is basically, when typing/scrolling through the code, pylance died with the message, also brought down the Jupyter kernel as well, no way to restart the kernel. Needs to reload the window to restart. |
Apologies. v2023.18.0 |
@csf90-uk @Tma2333-Scale and for those who have python extension 2023.6.0 or a newer version installed, were you seeing the exact same message |
Yes, the same error.
…On Wed, 1 Nov 2023 at 06:30, Stella ***@***.***> wrote:
@csf90-uk <https://github.com/csf90-uk> @Tma2333-Scale
<https://github.com/Tma2333-Scale> and for those who have python
extension 2023.6.0 or a newer version installed, were you seeing the exact
same message You may install and use any number of copies of the software
only with Microsoft Visual Studio..., or did you experience a different
Pylance crash?
—
Reply to this email directly, view it on GitHub
<#5019 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXMSZMAMFCOG7F4WIBDVVTLYCHT7PAVCNFSM6AAAAAA6SFTW7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBYGQ4DCMJSHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Same error here. VS Code version: version 1.83 |
Same here, only downgrading pylance worked. |
Most recent VSCode, pylance, etc. For me, it's breaking on the conda environment provided by ArcGIS Pro 3.1.3, which uses python v3.9.16. Worked "fine" (although pylance can't produce intellisense for all submodules of |
@quillaja I am sorry to hear that the latest pylance didn't work as expected but we will need more info to find out why that happened. providing screenshots as above (please make sure info underlined is shown in the screenshots) would help us to find out root issue! thank you |
can you show us not only that said, your screen shows different issue than this issue - you probably want to open a new issue so we can take a look rather than mixing with this issue. thank you. by the way, |
@quillaja I think your particular issue should be fixed by the latest pylance prerelease (2023.10.53) |
feedback my timeline:
|
@neljo8m thank you very much for the screenshot. is your dev environment asking since I tried on |
@liuxhit can you share the screenshot? |
Yes, I'm using # %%
# run some python code here
v = "test"
print( f"{v=}" )
# %% When I pressed <Shift+Enter> to run that in Jupyter, it ran fine. |
@neljo8m there is a separate jupyter related issue that is fixed in pylance |
You see the version of the Python extension I am using. So it looks like that does not apply to me. |
are you referring jupyter issue or |
Sorry, I was not clear. |
This issue has been fixed in prerelease version 2023.11.12, which we've just released. You can find the changelog here: CHANGELOG.md |
@bschnurr Thank you for announcing.
You mean version 2023.11.12? |
Yes, thanks. Fixed above. |
This issue is still (again?) happening on version 2024.12.3 of the Python extension. |
@ljnsn, questions for you:
We don't maintain a mapping of compatible historical versions of the Pylance and Python extensions. My recommendation would be to update to the latest of both. |
@debonte thanks for the quick response!
I understand, but the versions I'm using are the latest ones, aren't they? |
Oh, I'm sorry. I forgot that the Python extension has a different versioning scheme than us. I was interpreting xxxx.12.3 as a December release and didn't even look at the year.
Is this VS Code OSS then? Pylance is only supported in the official builds. Try downloading and installing from the VS Code website and I think you'll find that it works. |
Yes, it's a version of VS Code OSS. I previously never had any issues with Pylance/Python on this build, even though it's not officially supported. I'll wait for an update from the repo maintainer and see if it works with 1.92.x, otherwise I'll have to keep it updated myself. |
Environment data
Code Snippet
XXX
Repro Steps
Since I‘m using Python 3.5.4, I switched Python extension to v2020.8.109390 so that I can use the debugger. In previous versions everything works fine until v2023.10.50. I got
Request initialize failed with message: You may install and use any number of copies of the software only with Microsoft Visual Studio ...
, but I actually did not do anything it listed above.Expected behavior
Python extension works fine
Actual behavior
Logs
Output from Python Language Server:
The text was updated successfully, but these errors were encountered: