-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
Implement PEP 768 – Safe external debugger interface for CPython #131591
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Will this be released with 3.14? Should we prepare some basic support for pdb together with it? |
Yes that's the plan.
Yeah but as a separate PR for sure as this one just adds the basic functionality. 👍 We will try to land it next week |
Co-authored-by: Ivona Stojanovic <[email protected]> Co-authored-by: Matt Wozniski <[email protected]>
Signed-off-by: Pablo Galindo <[email protected]>
Signed-off-by: Pablo Galindo <[email protected]>
Seems like the interface is added, hurray! Do you want to work on the initial pdb support or do you want me to work for it? |
@gaogaotiantian Can you take a look at #132451 |
Co-authored-by: Ivona Stojanovic <[email protected]> Co-authored-by: Matt Wozniski <[email protected]>
Add a developer-facing document describing the protocol used by remote_exec(pid, script) to execute Python code in a running process. This is intended to guide debugger and tool authors in reimplementing the protocol.
Add a developer-facing document describing the protocol used by remote_exec(pid, script) to execute Python code in a running process. This is intended to guide debugger and tool authors in reimplementing the protocol.
See PEP-768
Linked PRs
The text was updated successfully, but these errors were encountered: