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

Why a separate python Interpreter variable? #6

Open
boatcoder opened this issue Dec 3, 2021 · 0 comments
Open

Why a separate python Interpreter variable? #6

boatcoder opened this issue Dec 3, 2021 · 0 comments

Comments

@boatcoder
Copy link

This already exists in settings, why add a different pythonInterpreter?

"python.defaultInterpreterPath"

I guess for backward compatibility you could look for the DTR variable first and then fallback to python.defaultInterpreterPath

I set my venv before I launch vscode but none of that seems to get into the vscode environment which is a pity.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@boatcoder