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

Merge Debugger support with cell hashing code #3297

Closed
IanMatthewHuff opened this issue Jun 28, 2019 · 2 comments
Closed

Merge Debugger support with cell hashing code #3297

IanMatthewHuff opened this issue Jun 28, 2019 · 2 comments
Assignees

Comments

@IanMatthewHuff
Copy link
Member

Merge the debugging support and the shell hashing code to work together to correctly map jupyter execution to .py file breakpoints.

@IanMatthewHuff IanMatthewHuff self-assigned this Jun 28, 2019
@YoniChechik
Copy link

Does it means that one can debug with breakpoints in interactive mode?

@IanMatthewHuff
Copy link
Member Author

IanMatthewHuff commented Jul 1, 2019

@YoniChechik . Debugging as an overall goal is currently in progress right now. Currently we support the very basics of debugging (attaching the debugger, you can hit a breakpoint() in cell code) but we don't currently map anything back to source files so debugger break points in code will not currently be hit and when you break in the debugger you will just see a temporary file of the cell code that you sent to jupyter. The work that we are currently doing now, but is not checked in, is to make that .py file line -> jupyter code cell mapping so that you can place breakpoints in your .py code and hit them.

@rchiodo rchiodo assigned rchiodo and unassigned IanMatthewHuff Jul 2, 2019
@rchiodo rchiodo closed this as completed Aug 6, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Aug 13, 2019
@microsoft microsoft unlocked this conversation Nov 14, 2020
@DonJayamanne DonJayamanne transferred this issue from microsoft/vscode-python Nov 14, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants