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

Opening a new terminal does not auto activate (env) #6437

Closed
level42ca opened this issue Jul 3, 2019 · 2 comments
Closed

Opening a new terminal does not auto activate (env) #6437

level42ca opened this issue Jul 3, 2019 · 2 comments
Assignees

Comments

@level42ca
Copy link

I can't seem to get my Python venv to auto activate. I'm not sure why, and was hoping someone could help me out.

I've tried different shells (Bash, Powershell, CMD) and none seem to activate the venv.

If I manually activate the env then it works.

This is my settings.json if this helps:

{
    "python.pythonPath": "env\\Scripts\\python.exe"
}

Not sure what else would be required to troubleshoot this.

vsver

@level42ca level42ca added the triage-needed Needs assignment to the proper sub-team label Jul 3, 2019
@level42ca
Copy link
Author

Seems to work if I remove other folders from my work space, but why?

@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jul 3, 2019
@DonJayamanne
Copy link

Duplicate of #3325

@DonJayamanne DonJayamanne marked this as a duplicate of #3325 Jul 3, 2019
@ghost ghost removed the triage label Jul 3, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jul 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants