forked from DonJayamanne/pythonVSCode
- Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug
Milestone
Description
Environment data
- VS Code version: 1.37
- Extension version (available under the Extensions sidebar): 2019.8.29288
- OS and version: Windows 10 1903
- Python version (& distribution if applicable, e.g. Anaconda): Python 3.7.3 64-bit
- Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
- Relevant/affected Python packages and their versions: N/A
- Jedi or Language Server? (i.e. what is
"python.jediEnabled"set to; more info How to update the language server to the latest stable version #3977): Jedi
Expected behaviour
Running the Python: Create Terminal command should properly activate my terminal using Activate.ps1
I expect to see this
Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. Try the new cross-platform PowerShell https://aka.ms/pscore6 Loading personal and system profiles took 1881ms. D:\MyProject [master ≡ +1 ~7 -0 !]> d:/MyProject/venv/Scripts/Activate.ps1 D:\MyProject [master ≡ +1 ~7 -0 !]> Actual behaviour
The command activates my terminal with activate.bat
This is what I see
Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. Try the new cross-platform PowerShell https://aka.ms/pscore6 Loading personal and system profiles took 1881ms. D:\MyProject [master ≡ +1 ~7 -0 !]> d:/MyProject/venv/Scripts/activate.bat D:\MyProject [master ≡ +1 ~7 -0 !]> Steps to reproduce:
- Run the
Python: Create Terminalcommand.
PhilMacKay, marsfan, a-gn and dan-osull
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug