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

Unblocking Method added #12

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
+18 −2
Open

Unblocking Method added #12

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7493edf
Unblocking Method added
arkaprovaz Jun 23, 2019
afd0860
Update README.md
arkaprovaz Jun 23, 2019
63f25dd
Update README.md
arkaprovaz Jun 23, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 18 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,28 @@
PSCondaEnvs
PowerShell Conda Integration
===========

Drop in replacement scripts that replicate Conda's activate/deactivate functions in Powershell.


### Installation:
Simply copy activate.ps1 and deactivate.ps1 into your Anaconda\Scripts directory. You may need to remove or rename the existing BAT files but the PS1 versions seem to get precedence.

### Path:
Usually the path is `C:\Users\{USERNAME}\Anaconda3\condabin\`

### Setting Execution Policy:
The file is not digitally signed so the PowerShell will prevent it from running. To unblock the files from Execution Policy run the commands:

`Unblock-File -Path C:\Users\{USERNAME}\Anaconda3\condabin\activate.ps1`

`Unblock-File -Path C:\Users\{USERNAME}\Anaconda3\condabin\deactivate.ps1`

Replace the `{USERNAME}` section with your username.

### Commands for managing the environments in PowerShell
`activate {environment_name}`

`deactivate {environment_name}`

### Added Features:
The optional -UpdateRegistry switch has been added which will update the Python installpath to be the activated virtualenv. I added this for installing compiled modules which detect the Python path from the registry.
THIS SHOULD BE USED WITH EXTREME CAUTION! This has only been tested on my system and is hardcoded to the 2.7 installpath. This setting is also persistent unlike the session-based ephemeral virtualenv activation. Deactivate.ps1 will detect and prompt for reverting the change if a virtualenv hasn't been properly deactivated.
Expand Down