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

Specify the PowerShell virtual environment activation script as Activate.ps1 #2607

Closed
brettcannon opened this issue Sep 17, 2018 · 1 comment
Closed

Specify the PowerShell virtual environment activation script as Activate.ps1 #2607

brettcannon opened this issue Sep 17, 2018 · 1 comment
Assignees
@brettcannon
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug

Comments

@brettcannon
Copy link
Member

Currently the activation script is lower-cased which won't work on e.g. PowerShell Core on Linux.
@brettcannon brettcannon added bug Issue identified by VS Code Team member as probable bug needs PR labels Sep 17, 2018
@brettcannon brettcannon self-assigned this Sep 17, 2018
@brettcannon
Copy link
Member Author

Can also probably make sure the directory name is Scripts.

@gramster gramster added area-environments Features relating to handling interpreter environments and removed area-environments Features relating to handling interpreter environments feature-interpreter labels Oct 10, 2019
@luabud luabud removed the -review- label Dec 3, 2019
@brettcannon brettcannon mentioned this issue Feb 5, 2020
Merged
10 tasks
@ghost ghost removed the needs PR label Feb 6, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Feb 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@brettcannon brettcannon

Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@brettcannon @gramster @luabud