You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked to make sure that this issue has not already been filed
Expected Behavior
By default, whether using Anaconda or some other installation of Python, virtualenv should be started with a reference to python rather than python3. An update to the documentation or a separate section containing this improvement + the one below opens the project to easier contribution.
The starting documentation should provide different instructions (open the ps1 script, not bat) if the user is using PowerShell for clarity with regard to setting up virtualenv.
For example, under the current documentation, the file referenced will not work at all using PowerShell or the Visual Studio Code Integrated Terminal. A reference or note mentioning this would ease the cloning of the project dramatically while also presenting a standardized setup process for those using PowerShell.
Current Behavior
The documentation does not highlight this behavior and targets the following file:
Given permission, I'd like to open a pull request addressing this in the documentation.
The text was updated successfully, but these errors were encountered:
JosephSemrai
changed the title
PowerShell documentation
Documentation Improvements for Windows + PowerShell
Dec 28, 2019
Prerequisites
Expected Behavior
python
rather thanpython3
. An update to the documentation or a separate section containing this improvement + the one below opens the project to easier contribution.For example, under the current documentation, the file referenced will not work at all using PowerShell or the Visual Studio Code Integrated Terminal. A reference or note mentioning this would ease the cloning of the project dramatically while also presenting a standardized setup process for those using PowerShell.
Current Behavior
The documentation does not highlight this behavior and targets the following file:
![image](https://user-images.githubusercontent.com/29003194/71550541-034be380-29a1-11ea-91d6-928443299cb5.png)
Given permission, I'd like to open a pull request addressing this in the documentation.
The text was updated successfully, but these errors were encountered: