Add debugpy to dependencies.

[FledgeXu]

Fix #10.

[codecov[bot]]

Codecov Report

Patch and project coverage have no change.

Comparison is base (708ac2b) 100.00% compared to head (1498d61) 100.00%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #13 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 1 1 Lines 8 8 Branches 1 1 ========================================= Hits 8 8 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

[rgaudin]

Thank you ; could you provide some brief doc on how to use it?

• what editor and plugin are needed (I could only make it work with VSCode).
• sample invoke task to lauch a project with it enabled?
• How does it integrates with the editor? Can you set breakpoints directly in the UI or must them be set in the code?

[FledgeXu]

Sure, but where should I add the document?

[rgaudin]

Here's fine. I wonder if some might get into the repo or if it's only gonna be in the Wiki

[FledgeXu]

I wonder if some might get into the repo or if it's only gonna be in the Wiki

We can mention it in the Wiki.

what editor and plugin are needed (I could only make it work with VSCode).

VScode: Python extension, NeoVim: nvim-dap, Vim: vimspector, Emacs: dap-mode. For the IDEs, I think it's not necessary.

sample invoke task to lauch a project with it enabled?

No, We don't need that. It's editors/plugins' job to enable it.

How does it integrates with the editor?

Different editors/plugins have different ways to integrate it. But I think most plugins just naturally support the VScode's json config file. Overall, you need to write a config file to tell your editors/plugins how to start the project and it should be fine.

Can you set breakpoints directly in the UI or must them be set in the code?

Of course, the breakpoints can be set in the UI.

[rgaudin]

OK then I think we're OK for now.