is this meant to be a library (aka import debugpy) or application ($ debugpy ...)?

@jonringer It's meant as both. It's normally used as an application:

python -m debugpy --listen localhost:5678 myfile.py

but you can also start a server by using it as a library:

import debugpy
debugpy.listen(5678)
debugpy.wait_for_client()  # blocks execution until client is attached

However, it doesn't create a bin wrapper, it must be started with python -m.

However, it doesn't create a bin wrapper, it must be started with python -m.

I wonder why they didn't do that, it's like 4 lines in a setup.py

@jonringer It looks like they have an issue open for it. I guess they never got around to it, even though it's trivial.

On the latest unstable channel, one test seems to be failing for me: tests/debugpy/test_exception.py::test_systemexit. Are you able to reproduce this?

On the latest unstable channel, one test seems to be failing for me: tests/debugpy/test_exception.py::test_systemexit. Are you able to reproduce this?

do you mind posting the failure. if it's specific to the nix sandbox, it's fine to skip it. But test failures may also indicate that something is truely broken.

do you mind posting the failure. if it's specific to the nix sandbox, it's fine to skip it. But test failures may also indicate that something is truely broken.

Hmm, I can't seem to reproduce the failure right now. I made a fresh Python build with debugpy just now in a clean environment with the latest master branch of nixpkgs, and all the tests passed. But last night when I was upgrading my packages (including this package, which OP had posted on NUR) with the latest nixos-unstable channel, I observed that one test case (test_systemexit) failing. I suppose we can ignore it for now, and if it comes up again, I'll report back.

@leungbk I can't seem to reproduce the issue either, do you have the commit hash where it was a problem?

@MetaDark The build failure occurred when I was upgrading my system packages (not the cleanest environment) on the latest nixos-unstable channel. But after visiting the commit appearing to correspond to that point in the unstable channel, I cannot reproduce the failure in a fresh environment with nothing but Python 3 and debugpy. Everything appears to build fine.

I'll bring it up in the future if it comes up again and I figure out how to reproduce. Sorry for the noise.

@GrahamcOfBorg build python3Packages.debugpy

I think this looks good for now, most of my issues are with upstream not having an "entry_point" in their setup.py.