Remove Run Button Contributions from Python Extension

[rongxin-liu]

No description provided.

[rongxin-liu]

@dmalan Hmm, ran into a few unknown complications while building the extensions. No clear signs of what the issue was so far.

With the changes to the packages.json files, we can stop the Run buttons from showing up in the VS Code editor, which is good. But now I’ve hit a problem where I can’t bring up the Python debugger for some reason. Reinstalling the Python debugger from the marketplace fixes it, but I still don’t know what the difference is between our custom build and the published one. As far as I can tell, the only real difference is the UI—nothing substantial.

Also noticed that the version published on the VS Code marketplace doesn’t actually exist on the corresponding GitHub repo. So, we can’t fork the latest build and make minor changes while still making sure it works with the latest VS Code release.

[dmalan]

Is there any way to modify the natively installed extensions' JSON within the codespace so as to override their default values? Or does that have to be done at the extensions' build time?

[rongxin-liu]

Is there any way to modify the natively installed extensions' JSON within the codespace so as to override their default values? Or does that have to be done at the extensions' build time?

We could do that via postCreateCommands or our extension. However, the changes won’t take effect until the Codespace window is reloaded. This means that every time students run update50 or the extension is updated automatically, the run button will reappear, and it will only be hidden again after the Codespace window is reloaded.

[rongxin-liu]

Ok, I’m going to do this via our cs50.vsix extension instead: cs50/cs50.vsix#31

It is much less intrusive. However, after package.json files are changed, those python extensions need to be reactivated for the changes to take effect.

[mverdicchio]

@rongxin-liu Hi Ronxin - I had a student come in for help today. He couldn't use the debugger either. I tried what you said -- uninstalling and reinstalling from the marketplace, but we still kept getting a "failed to resolve env /python" error. When I try on my codespace, the debugger worked fine. We've both recently run update50 -f.
Do you think his problem is related to this update you're working on?

[rongxin-liu]

I don’t think that’s related but would be nice to see a screenshot of the issue.

…

On Thu, Oct 2, 2025 at 15:39 Michael Verdicchio ***@***.***> wrote: *mverdicchio* left a comment (cs50/codespace#183) <#183 (comment)> @rongxin-liu <https://github.com/rongxin-liu> Hi Ronxin - I had a student come in for help today. He couldn't use the debugger either. I tried what you said -- uninstalling and reinstalling from the marketplace, but we still kept getting a "failed to resolve env /python" error. When I try on my codespace, the debugger worked fine. We've both recently run update50 -f. Do you think his problem is related to this update you're working on? — Reply to this email directly, view it on GitHub <#183 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACQZ3MMENW4UULJTWXTSPHD3VV5PTAVCNFSM6AAAAACHVHEFMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNRSGY4DAMJZHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>