add debugpy-adapter entrypoint

[TheJJ]

so the adapter can also be launched inside a venv even though debugpy is not installed in the venv.

ref #1868

[TheJJ]

@microsoft-github-policy-service agree

[rchiodo]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[rchiodo]

Once this goes through we should probably update the wiki page to explain how it can be started:
https://github.com/microsoft/debugpy/wiki/Command-Line-Reference

[TheJJ]

I don't think the failed ci runs are related to my changes?

[rchiodo]

Yeah I agree. I'll submit.

[rchiodo]

Can you update the wiki with this extra supported command line?

[TheJJ]

I don't think I have the permissions to edit the wiki? And should the -m debugpy invocations described there also be replaced by the entry-point? I'd of course leave a note that running as module still works.

[rchiodo]

I updated all of the command line references to say debugpy now instead.

You added support for calling the adapter directly, right? debugpy-adapter? How would you use that outside of a venv?

With the full path?

C:\Users\<user>\.venv\scripts\debugpy-adapter --listen 5678 foobar.py

[TheJJ]

No, this doesn't solve the venv-usage yet, I fear, but is a step towards it. What the launcher now allows is launching despite being in a venv (where debugpy isn't installed). What remains to be done is that debugpy now is aware of the venv, I think.

One idea would be adding the venv site package path to the path, and removing system site packages if the venv config disallows system-site-packages.

What do you think?

[rchiodo]

Sorry but I'm confused. I thought you were doing the opposite. Debugpy can already be run outside of a venv. It's actually how VS code itself works.

[TheJJ]

Yes, that's what I'm trying to achieve, but using the adapter. How is debugpy launched in vscode so this works properly?

[rchiodo]

The command line looks like so:

'c:\Users\rchiodo\AppData\Local\pypoetry\Cache\virtualenvs\single-a0w9Kr8b-py3.11\Scripts\python.exe' 'c:\Users\rchiodo\.vscode\extensions\ms-python.debugpy-2025.4.1-win32-x64\bundled\libs\debugpy\launcher' '52716' '--' 'c:\Users\rchiodo\source\testing\test_move_folders\parent_folder\target_stuff\human.py'

Where

• c:\Users\rchiodo\AppData\Local\pypoetry\Cache\virtualenvs\single-a0w9Kr8b-py3.11\Scripts\python.exe is my virtual environment
• c:\Users\rchiodo.vscode\extensions\ms-python.debugpy-2025.4.1-win32-x64\bundled\libs\debugpy\launcher is a python file that ships with the debugpy extension.

That launcher package accomplishes what you're trying to do I believe.