Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

VIRTUAL_ENV not unset by deactivate.bat on Windows #9

Closed
vbabiy opened this Issue · 3 comments

3 participants

@vbabiy

Hi, deactivate.bat doesn't unset VIRTUAL_ENV environment variable on Windows, using virtualenv 1.5.1. Linux counterpart deactivate instead does.

C:\Sandbox\python>virtualenv foo
New python executable in foo\Scripts\python.exe
Installing setuptools.....................done.

C:\Sandbox\python>cd foo

C:\Sandbox\python\foo>Scripts\activate.bat
(foo) C:\Sandbox\python\foo>echo %VIRTUAL_ENV%
C:\Sandbox\python\foo

(foo) C:\Sandbox\python\foo>Scripts\deactivate.bat
C:\Sandbox\python\foo>echo %VIRTUAL_ENV%
C:\Sandbox\python\foo

@piotr-dobrogost

This issue doesn't allow Python Launcher to work with virtualenv - https://bitbucket.org/vinay.sajip/pylauncher/issue/15/

@piotr-dobrogost

It seems a fix is to simply unset VIRTUAL_ENV environment variable in deactivate.bat, isn't it?
If so I can make a pull with this change.

@piotr-dobrogost piotr-dobrogost referenced this issue in davidmarble/virtualenvwrapper-win
Open

Make mkvirtualenv WORKON_HOME environment variable aware #21

@piotr-dobrogost piotr-dobrogost referenced this issue from a commit in piotr-dobrogost/virtualenv
@piotr-dobrogost piotr-dobrogost Clear VIRTUAL_ENV environment variable. Fixes issue #9. 25cbf41
@Ivoz
Owner

Closed by 25cbf41

@Ivoz Ivoz closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.