Pylance Copilot Server is activated even if "python.languageServer": "None" #7346
Replies: 2 comments 3 replies
-
|
Hi @trinhanhngoc, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime. Similar Issues (FYI only, not solutions) The following issues may or may not be related to your report. They are provided for reference only, as they may describe similar symptoms or relate to the same feature, but may not be the same issue.
The team will respond to your issue shortly. Please note this is a trial feature and may not be fully accurate. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or was incorrect, please give it a 👎. Your feedback helps us improve! |
Beta Was this translation helpful? Give feedback.
-
|
Transferred to a question as this isn't a bug. Yes that is expected. Pylance provides context to the copilot APIs so that copilot works better. It needs to run a server in the background for that to work. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Hello Pylance team. I just noticed that after I enable Copilot, Pylance language server is activated under the new name Pylance Copilot Server even if I disabled it by setting
"python.languageServer": "None". Is this expected behavior?VSCode
Pylance 2025.6.1
Beta Was this translation helpful? Give feedback.
All reactions