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

[Feature Request]: Switch to debugpy rather than vscode-python #109

Closed
3 tasks
puremourning opened this issue Jan 31, 2020 · 2 comments · Fixed by #115
Closed
3 tasks

[Feature Request]: Switch to debugpy rather than vscode-python #109

puremourning opened this issue Jan 31, 2020 · 2 comments · Fixed by #115

Comments

@puremourning
Copy link
Owner

See #108 and #105 and a number of other complaints - we can't really rely on the way we're using vscode-python's typescript debug adapter anymore.

  • : Find a way to install debugpy using install_gadget.py
  • : Make install_gadget.py write a compatibility adapter config (should be trivial)
  • : Ensure that the regression tests still pass
@puremourning
Copy link
Owner Author

Unfortunate this doesn’t work in neovim. Maybe here is a workaround like setting the env globally before starting the term and then unsettling it.

@puremourning
Copy link
Owner Author

It works in neovim since #110

@puremourning puremourning mentioned this issue Feb 8, 2020
Merged
@mergify mergify bot closed this as completed in #115 Feb 8, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Switch to debugpy rather than vscode-python puremourning/vimspector
1 participant
@puremourning