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

Deprecate/remove jupyter.selectjupyteruri as an extensibility point for 3rd party extensions #13300

Closed
1 of 3 tasks
Tracked by #12832
DonJayamanne opened this issue Apr 11, 2023 · 1 comment · Fixed by #13819
Closed
1 of 3 tasks
Tracked by #12832
Assignees
Labels
debt Code quality issues notebook-remote Applies to remote Jupyter Servers
Milestone

Comments

@DonJayamanne
Copy link
Contributor

DonJayamanne commented Apr 11, 2023

Currently this is used internally and this command seems to have been modifeid to support it as an extensibility point for 3rd party extensions

@DonJayamanne DonJayamanne added notebook-remote Applies to remote Jupyter Servers debt Code quality issues notebook-kernel-remote labels Apr 11, 2023
@DonJayamanne DonJayamanne self-assigned this Apr 11, 2023
@C-SELLERS
Copy link
Contributor

In reference to your comment on #8902

@C-SELLERS are you still using the command jupyter.selectjupyteruri
I'm considering deprecating this command and getting extension authors to use the API registerRemoteServerProvider

Not for my own application.

@Martin-Molinero heads up, this may still be in use by QuantConnect vscode terminal

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debt Code quality issues notebook-remote Applies to remote Jupyter Servers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants