Skip to content
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

Implement Cell Debugging - Notebook Editor #1450

Closed
IanMatthewHuff opened this issue Oct 1, 2019 · 3 comments
Closed

Implement Cell Debugging - Notebook Editor #1450

IanMatthewHuff opened this issue Oct 1, 2019 · 3 comments

Comments

@IanMatthewHuff
Copy link
Member

Breakdown of approximate timing for our native debugging spec

@rchiodo
Copy link
Contributor

rchiodo commented Oct 10, 2019

Two different options here

  1. Use VS code's debugger
    • Spike to prevent VSC from opening a document (skip frame, etc)
    • DAP in the middle (3d)
  2. Use the DAP ourselves and talk to the debugger/handle all of the messages ourselves.
    • Extension as debug controller
    • Variable explorer (1d)
    • Debugger owns variable eval (1w)
    • Custom toolbar 1d

Stuff for both
* Call DAP on PTVSD (2w)
* Margins (1w)

@jmew jmew changed the title Time costing for debugging spec Implement Cell Debugging - Notebook Editor Oct 10, 2019
@jmew
Copy link
Contributor

jmew commented Oct 10, 2019

@DonJayamanne DonJayamanne transferred this issue from microsoft/vscode-python Nov 13, 2020
@DavidKutu
Copy link

dupe of #1652

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants