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.

Sign up for GitHub

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

Jump to bottom

Built-in variables inspector and API #13497

Open
roblourens opened this issue Nov 27, 2022 · 7 comments
Open

Built-in variables inspector and API #13497

roblourens opened this issue Nov 27, 2022 · 7 comments
Labels
enhancement pkg:debugger status:Needs Discussion

Comments

@roblourens
Copy link

Hi, I work on VS Code notebooks, and our Jupyter extension's variables view. I heard a rumor that Jupyter Lab might work on a built-in variable inspector. By "variable inspector" I mean the kind of thing that the variable inspector extension does- https://jupyter-contrib-nbextensions.readthedocs.io/en/latest/nbextensions/varInspector/README.html give a list of variables/values in the kernel while not debugging.

I'm searching around but don't see any public discussions about this, is this rumor true? And is there anything that you can point me to? I'm also assuming that a new API would be required to drive this, and I'm interested in any details about that as well.

And let me know if there is somewhere else I should raise this or file an issue- thanks!
@roblourens roblourens added the bug label Nov 27, 2022
@jupyterlab-probot jupyterlab-probot bot added the status:Needs Triage Applied to new issues that need triage label Nov 27, 2022
@welcome
Copy link

welcome bot commented Nov 27, 2022

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

@krassowski
Copy link
Member

Hi @roblourens nice to have you here. There is a prior discussion in: #443 but I do not recall any recent discussion of current progress of making a debugger-less variable inspector. It might be worth asking during the JupyterLab weekly call if you have time on Wednesday.

As for what currently is available, we do have a variable viewer in the debugger mode indeed. Currently we extend the debugger protocol with inspectVariables and richInspectVariables request and render the returned MIME bundle (#10299). It would be nice if that could be upstreamed in DAP. And there are third-party extensions for Jupyter Notebook and JupyterLab, but we would ideally standardise this (in my opinion around MIME bundles with data streams) to avoid having multiple (possibly fragile) implementations.

@fcollonval
Copy link
Member

FYI there is at least that extension in JupyterLab: https://github.com/lckr/jupyterlab-variableInspector

@roblourens
Copy link
Author

Thanks @krassowski. That's interesting, I will look at your DAP extensions. I was just a bit too late coming back to this notification for this week, so maybe I will be able to join in the future.

@JasonWeill JasonWeill mentioned this issue Dec 1, 2022
Closed
@andrii-i andrii-i mentioned this issue Dec 8, 2022
Open
@roblourens
Copy link
Author

Interesting. It looks like this issue was on the agenda for a meeting a couple weeks ago, are there notes/recording or can you tell me what was discussed?

@fcollonval
Copy link
Member

@roblourens each new issues get tag status:Needs triage. Then a weekly (unrecorded) meeting is carrying out a triage of those issues. Hence the link appearing to the Weekly Triage meeting.

@danieltomasz
Copy link

danieltomasz commented May 15, 2023 •
edited
Loading

FYI there is at least that extension in JupyterLab: https://github.com/lckr/jupyterlab-variableInspector

This extension seems to don't work with jupyterlab => 3.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement pkg:debugger status:Needs Discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@roblourens @krassowski @danieltomasz @fcollonval @JasonWeill