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

Provide code mapping for debugger integration of the interactive window #3288

Closed
rchiodo opened this issue Jun 24, 2019 · 5 comments
Closed
Assignees

Comments

@rchiodo
Copy link
Contributor

rchiodo commented Jun 24, 2019

Provide the necessary infrastructure to map cell execution to hash codes in the debugger.

@rchiodo rchiodo self-assigned this Jun 24, 2019
@ihnorton
Copy link

ihnorton commented Jul 23, 2019

Does this include making line numbers clickable when a Traceback is displayed in the interactive window? Ideally for non-debugger execution as well. (sorry if I overlooked an existing issue)

@rchiodo
Copy link
Contributor Author

rchiodo commented Jul 23, 2019

Sorry, that is not a feature we currently have.

There is a goto source button, but you have to determine which line matches yourself.

@rchiodo
Copy link
Contributor Author

rchiodo commented Jul 23, 2019

This code mapping issue is for mapping the hashed source code that jupyter generates to real code living in a file.

@ihnorton
Copy link

In that case, feature suggestion: make the line numbers clickable when tracebacks are shown in the interactive window, for errors during "normal" execution. It seems like that would utilize the same source-map infrastructure as the debugger, but perhaps I'm misunderstanding what you mean by hashed source that jupyter generates. Thanks!

@rchiodo
Copy link
Contributor Author

rchiodo commented Jul 23, 2019

I created a new issue for your suggestion:
https://github.com/microsoft/vscode-python/issues/6679

Thanks.

@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

2 participants