@karthiknadig I still can't get pylance ever started locally to test. Would you be able to assist?

this is all I see in the output pane:

2025-05-07 17:40:16.535 [info] Experiment 'All' is active2025-05-07 17:40:16.535 [info] Native locator: Refresh started2025-05-07 17:40:16.535 [info] > pyenv which python2025-05-07 17:40:16.535 [info] cwd: .2025-05-07 17:40:16.609 [info] > conda info --json2025-05-07 17:40:16.642 [info] > /opt/anaconda3/bin/conda info --json2025-05-07 17:40:29.634 [info] Discover tests for workspace name: undefined - uri: /Users/kylei/Library/Application Support/Code/User/settings.json2025-05-07 17:40:38.359 [info] Discover tests for workspace name: undefined - uri: /Users/kylei/Library/Application Support/Code/User/settings.json

Rich mentionedhere that pylance needs to be installed in the extensions folder. I don't have pylance source so I can't get that one, but I do have the release pylance there (because it's installed normally). I also tried cloning this repo into the extensions folder but that made no difference.

Thanks!

@rchiodo can you help with this. I suspect we may need to re-load here.

The output looks like it's not even trying to start pylance. Meaning that would be entirely in the Python extension.

I'll try building this branch and see what I get.

Yeah this works for me. I just followed the steps in the contributing wiki.

• npm i
• pip install nox
• nox --session setup_repo
• Open in VS code
• Hit F5

I had pylance just installed like normal.

When I set this it seems it's not starting Pylance though:

Or it's killing it as I get this in our log:

2025-05-07 17:22:52.442 [info] Starting inspector on 127.0.0.1:6600 failed: address already in use2025-05-07 17:22:54.277 [info] [Info  - 5:22:54 PM] (18332) Server root directory: file:///c%3A/Users/rchiodo/.vscode/extensions/ms-python.vscode-pylance-2025.4.103/dist2025-05-07 17:22:54.278 [info] [Info  - 5:22:54 PM] (18332) Pylance language server 2025.4.103 (pyright version 1.1.400, commit b962ffc2) starting2025-05-07 17:22:54.281 [info] [Info  - 5:22:54 PM] (18332) Starting service instance "notebook_errors" for workspace "c:\Users\rchiodo\source\testing\notebook_errors"2025-05-07 17:22:54.368 [info] [Info  - 5:22:54 PM] Server process exited successfully

I did some debugging. The changing of this setting seems to set off a cascade of events:

First this fires:

this.disposables.push(this.workspace.onDidChangeConfiguration((event:ConfigurationChangeEvent)=>{if(event.affectsConfiguration('python')){this.onDidChanged(event);}}),);

Well because the pyrefly setting is prefixed with python.

That causes the internal 'update' method to get called.

That in turn changes the 'languageServer' setting to a new value, which then causes another update.

That then causes this to fire

privateasynconDidChangeConfiguration(event:ConfigurationChangeEvent):Promise<void>{constworkspacesUris=this.workspaceService.workspaceFolders?.map((workspace)=>workspace.uri)??[];workspacesUris.forEach(async(resource)=>{if(event.affectsConfiguration(`python.languageServer`,resource)){awaitthis.refreshLanguageServer(resource);<---Thishere}elseif(event.affectsConfiguration(`python.analysis.pylanceLspClientEnabled`,resource)){awaitthis.refreshLanguageServer(resource,/* forced */true);}elseif(event.affectsConfiguration(`python.pyrefly.disableLanguageServices`,resource)){awaitthis.refreshLanguageServer(resource);}});}

Then we get another update for the pyrefly setting changes which then causes this to fire:

privateasynconDidChangeConfiguration(event:ConfigurationChangeEvent):Promise<void>{constworkspacesUris=this.workspaceService.workspaceFolders?.map((workspace)=>workspace.uri)??[];workspacesUris.forEach(async(resource)=>{if(event.affectsConfiguration(`python.languageServer`,resource)){awaitthis.refreshLanguageServer(resource);}elseif(event.affectsConfiguration(`python.analysis.pylanceLspClientEnabled`,resource)){awaitthis.refreshLanguageServer(resource,/* forced */true);}elseif(event.affectsConfiguration(`python.pyrefly.disableLanguageServices`,resource)){awaitthis.refreshLanguageServer(resource);<---Thishere}});}

Which in effect doesn't turn off the language server. Well it actually depends upon what the setting was on startup. It either turns it on and then off again or turns it on twice.

I think the python extension needs to be changed to not double fire this event.

I did some debugging. The changing of this setting seems to set off a cascade of events:

First this fires:

this.disposables.push(this.workspace.onDidChangeConfiguration((event:ConfigurationChangeEvent)=>{if(event.affectsConfiguration('python')){this.onDidChanged(event);}}),);

Well because the pyrefly setting is prefixed with python.

That causes the internal 'update' method to get called.

That in turn changes the 'languageServer' setting to a new value, which then causes another update.

That then causes this to fire

privateasynconDidChangeConfiguration(event:ConfigurationChangeEvent):Promise<void>{constworkspacesUris=this.workspaceService.workspaceFolders?.map((workspace)=>workspace.uri)??[];workspacesUris.forEach(async(resource)=>{if(event.affectsConfiguration(`python.languageServer`,resource)){awaitthis.refreshLanguageServer(resource);<---Thishere}elseif(event.affectsConfiguration(`python.analysis.pylanceLspClientEnabled`,resource)){awaitthis.refreshLanguageServer(resource,/* forced */true);}elseif(event.affectsConfiguration(`python.pyrefly.disableLanguageServices`,resource)){awaitthis.refreshLanguageServer(resource);}});}

Are you sure this second update "This here" isn't caused by mypatch? To test these changed, I think we need to be on an older version of pyrefly. IInstall specific version...ed 0.12.1 when testing this.

Are you sure this second update "This here" isn't caused by mypatch? To test these changed, I think we need to be on an older version of pyrefly. I Install specific version...ed 0.12.1 when testing this.

Yeah, that made things a lot easier to get working. I pushed an update which I think should fix the problem. At least for me locally, with using pyrefly 0.12.1, the setting works as designed.

Are you sure this second update "This here" isn't caused by mypatch? To test these changed, I think we need to be on an older version of pyrefly. I Install specific version...ed 0.12.1 when testing this.

Yeah, that made things a lot easier to get working. I pushed an update which I think should fix the problem. At least for me locally, with using pyrefly 0.12.1, the setting works as designed.

Awesome! Thanks for the fix. I can test in the morning. Did this fix the issue for both settings updates and on Pyrefly install?

No rush in getting this in until the next release. I'll just remove my pyrefly patch once these go into this extension (everything works fine right now with the hack).

Sorry I didn't realize there was a problem on install. That would likely have to be handled with something waiting for install of pyrefly.

Yeah install requires a restart of the extension host for the logic to work.

@karthiknadig do you know how the Python extension indicates 'restart' required on install? Maybe pyrefly can just set that same setting

@rchiodo I think this has to be handled in the on change handler. Some time ago we used to request reload of the extension on language server change by popping up a notification, and later triggering the reload window command. I think we removed it after we made it so you did not need to reload.

Yeah I looked at the VS code source. Restart Extensions isn't controlled by the extension at all. VS code decides based on if the extension is already running etc. So we'd have to listen to this event:https://github.com/microsoft/vscode/blob/2d6afddc470bf44f7e60fb5b6e6fdd08e771409b/src/vscode-dts/vscode.d.ts#L17320-L17321

@kinto0 Can you add this event or do you need help with this?

@kinto0 Can you add this event or do you need help with this?

sorry about my delay. we have such a big backlog of pyrefly bugs ahead of us from the release. Unfortunately, this one is low on the list because it actually does work now withmy workaround. It's more of a better engineering task. If you think it's important for pylance (example: someone else wants to add a LS to pylance with a similar setup) and want to help out , please do!