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

Fix up Python extension recommendations #15

Open
SaschaCowley opened this issue Aug 6, 2024 · 3 comments
Open

Fix up Python extension recommendations #15

SaschaCowley opened this issue Aug 6, 2024 · 3 comments

Comments

@SaschaCowley
Copy link
Member

Currently, our extensions.json lists both ms-python.python and ms-python.vscode-pylance, despite the fact that the Python extension installs Pylance by default. Since the extension works best with the Python Debugger extension installed, we should either:

  1. Remove the explicit recommendation of Pylance, and just rely on the other extensions recommended by the Python extension; or
  2. Add Python Debugger to the recommendations to make our recommendation explicit.
@seanbudd
Copy link
Member

seanbudd commented Aug 6, 2024

Is the python debugger extension useful/accessible?

@michaelDCurran
Copy link
Member

Is the python debugger extension useful/accessible?
Absolutely. It is required to run debug sessions in VS Code for Python projects, including break points, call stacks, watching variables, runtime execution of Python code within the debugged process.

@SaschaCowley
Copy link
Member Author

As Mick has said, yes. Additionally it's required (if you want to debug Python) for the remote debugging method I'm writing up. I can open a PR to include everything required for that method (launch.json and changes to extensions.json) all at once if that's preferable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants