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

Feature request: export more ptvsd-related commands as api #6909

Closed
kejxu opened this issue Aug 8, 2019 · 4 comments
Closed

Feature request: export more ptvsd-related commands as api #6909

kejxu opened this issue Aug 8, 2019 · 4 comments
Labels
area-debugging feature-request Request for new features or functionality

Comments

@kejxu
Copy link

kejxu commented Aug 8, 2019

Internal Team Ask (vscode-ros)

currently only getRemoteLauncherCommand() is exposed in vscode-python's api interface.

meantime, as described in ptvsd documentation, ptvsd could be used at entry (to launch a script/module), or while the (Python) process is running (to inject a ptvsd instance)

It would be nice if a new getInjectDebugServerCommand() api could be exposed.

@kejxu kejxu added triage-needed Needs assignment to the proper sub-team feature-request Request for new features or functionality labels Aug 8, 2019
@DonJayamanne
Copy link

DonJayamanne commented Aug 8, 2019

Note

@DonJayamanne DonJayamanne added area-debugging needs decision and removed triage-needed Needs assignment to the proper sub-team labels Aug 8, 2019
@luabud
Copy link
Member

luabud commented Oct 29, 2019

Closing it since once the work for #1078 is done, this API won't be needed as VS Code will be able to automatically connect to a process you want to connect to.

@luabud luabud closed this as completed Oct 29, 2019
@ghost ghost removed the needs decision label Oct 29, 2019
@kejxu
Copy link
Author

kejxu commented Oct 30, 2019

Closing it since once the work for #1078 is done

thanks for the update, are there any pull requests related to #1078? not able to find links from that issue's page

@luabud
Copy link
Member

luabud commented Oct 30, 2019

@kejxu Not yet, it's marked as "needs spec" so we can finish some design decisions before we work on it, but we may start working on it soon :)

@lock lock bot locked as resolved and limited conversation to collaborators Nov 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-debugging feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants