FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

variable provider for native repl by amunger · Pull Request #24094 · microsoft/vscode-python · GitHub

variable provider for native repl - #24094

Merged
Aaron Munger (amunger) merged 26 commits into
mainfrom
aamunger/variableProvider
Sep 18, 2024
Merged

Aaron Munger (amunger) merged 26 commits into
mainfrom
aamunger/variableProvider

Conversation

Copy link
Copy Markdown

fix #24066

Aaron Munger (amunger) changed the title Aamunger/variable provider variable provider for native repl Sep 11, 2024
Aaron Munger (amunger) added the feature-request Request for new features or functionality label Sep 11, 2024
Aaron Munger (amunger) marked this pull request as ready for review September 12, 2024 21:39
vs-code-engineering Bot added this to the September 2024 milestone Sep 12, 2024

Copy link
Copy Markdown
Member

You may need to rebase after this other PR is merged for the Smoke test issue: 2b4c2bf

Aaron Munger (amunger) added the skip package*.json package.json and package-lock.json don't both need updating label Sep 16, 2024
Aaron Munger (amunger) enabled auto-merge (squash) September 17, 2024 20:54
indexedChildrenCount: number;
}

interface NotebookVariableProvider {

Anthony Kim (anthonykim1) Sep 17, 2024
edited
Loading

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Aaron Munger (@amunger) Does the vscode engine need to be explicitly pinned?
We currently have

 "engines": {
        "vscode": "^1.94.0-20240913"
    },

also saw commit on vscode-distro so I think we are good.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

just has to be beyond that distro commit, and that version is, so it should work

function wrapScriptInFunction(scriptLines: string[]): string {
const indented = scriptLines.map((line) => ` ${line}`).join('\n');
// put everything into a function scope and then delete that scope
// TODO: run in a background thread

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Would running the script in the background give performance benefit?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

having a large number of variables could conceivably block execution as they are collected and putting this operation on a background thread would prevent that. the speed of safeRepr might make that unnecessary though.

Aaron Munger (amunger) merged commit 717e518 into main Sep 18, 2024
Aaron Munger (amunger) deleted the aamunger/variableProvider branch September 18, 2024 01:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature-request Request for new features or functionality skip package*.json package.json and package-lock.json don't both need updating

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support variable exploration in the native REPL

3 participants


Back | FazBrowse Home | New Git URL