Add support for pydevd --continue to allow launching an app without pausing#199
Add support for pydevd --continue to allow launching an app without pausing#199briandealwis wants to merge 3 commits intofabioz:mainfrom
pydevd --continue to allow launching an app without pausing#199Conversation
|
Hi Brian, can you elaborate a bit on when you'd use this? i.e.: In general this wouldn't be a good idea as it'd add the possibility of missing breakpoints until those are actually sent from the client, so, I'm curious on the use case here... |
|
Sorry Fabio, this got lost in my inbox. At its essence, we're interested in supporting debugging of Python micro-services as part of a Kubernetes-based application. The scenario is usually around a developer launching the app in a development environment, such that they control how inputs are fed into the system; it's not for live-debugging of a production or staging environment. So the developer is usually in control over initiating requests of the application, so the risk of missing breakpoint scenarios is small. Kubernetes has various readiness and liveness requirements for services, so a container that is paused waiting for a debugger to connect and resume execution can trigger a ripple effect across the system. |
|
Hi @fabioz — is it possible to get this committed? |
|
Sorry for the delay... this got lost on my side too :( Would it be ok for you to rename the argument from -- I think Also, can you create one test-case for this (to make sure that it won't break going further)? -- the related test should be in |
|
p.s.: if you need more pointers on the test case, please let me know. |
This PR adds a new flag to
pydevd,--continue, to start the application without waiting for the debugger connection. @etanshaul has been testing this with PyCharm with good results.I didn't find an obvious place to create a test around this and would appreciate a pointer for how to proceed.
Fixes #161