-
I'm running into all sorts of problems with my setup running certain commands (windows, cygwin, wsl) with poetry (in particular "poetry add source...")--certificate errors, 'is a directory' errors and one other I cant recall. If this was a simple import in python code I'd be able to just step into module code and get an idea of what's going on. And wouldn't mind passing on any issues I find to devs. However, I don't know how to do this type of debugging with a cli binary python command. (I'd prefer to do this in vscode, but if you can tell me in pycharm I can probaly translate the instructions.) I figure python -m poetry might be part of it. I see vscode supports module run configuration but I don't see how I get an entrypoint into it once I run. I don't see any mention of deveopment setup in the poetry documentation. I suppose I may be ablet o hack some main() entrypoint ina script which sends arguments to poetry module (not cli binary) and enter that way, but not quite sure where to enter or if that's even the best way. How can I debug poetry when I'm using it as a cli binary so I can set breakpoints (and even better, post-mortem debugging just before/after the cli/stderr warnings/errors are displayed. Is there any example of how to get started with a poetry debugging setup? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Found out how:
Then run main.py as the entry point. It should run your command and you can debug the errors As far as my issues (for anyone else):
|
Beta Was this translation helpful? Give feedback.
Found out how:
In VSCode use the following launch.conf:
Then run main.py as the entry point. It should run your command and you can debug the errors
As far as my issues (for anyone else):