Open musikele opened 4 months ago
debugpy is purely a DAP (debug adapter protocol) server/adapter implementation; it is not a DAP client like VSCode. The terms "listen" and "connect" in its API and CLI refer solely to the direction of connection between it and the client - you can have debugpy listen for an incoming connection from the client, or you can have the client listen and debugpy connect to it.
For your scenario, you should look at alternative DAP clients; this list is a good starting point. I'm not aware of any DAP client that is similar to pdb in UX, but if you just want something that is not tied to VSCode and capable of running in text mode, I would recommend looking at Vimspector - they specifically support debugpy.
That aside, given that the protocol is very high-level, making a custom pdb-like CLI wrapper around it should be fairly straightforward. If you go down that route, you can reuse the implementation of the messaging layer from debugpy, and perhaps also look at our test client that is used to drive debugpy functional tests.
Hi there, in my company many don't use VSCode. For this reason our main guidelines to debug are to use
pdb
orepdb
. (https://pypi.org/project/epdb/) However, in an effort to have just one library that works for all use cases, I'd like to have debugpy to work from command line too.I have tried this:
doesn't stop in debug.
I've also tried to use debugpy in python shell:
What is supposed to be this "command"?
Also, am I doing something that is intended to be used like this, or what? I think no, because there is no such reference on the web.