-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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.
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
Virtualenv Name Incorrect When Activated with Powershell Script #2090
Comments
A PR fixing this would be appreciated. |
Hello - Is this error specific to OP's environment and his packages installed in the environment? I tried creating a new virtualenv and didn't see the issue. Both cmd's activate and powershell's activate show the correct virtualenv name. |
Odd. I am no longer seeing it. I shall reopen if I can reproduce. |
I've ended up back here again. In powershell navigate to some network location using a mapped drive and create the virtual env:
Activate it. As shown here you may have to set the execution policy
Ok, all good. Now let's use exactly the same .venv on a UNC path...
Not only is the virtualenv name incorrect, but the activation isn't actually working, it just picks up whatever python is first on path.
virtualenv version 20.14.0 |
Issue
When using the
Activate.ps1
script, the name in parenthesis becomes(activate.ps1)
, as opposed to the name of the virtual environment when using the bat file.Environment
Provide at least:
pip list
of the host python wherevirtualenv
is installed:Output
Output of the virtual environment creation
Make sure to run the creation with
-vvv --with-traceback
:TheREDACTED_PATH
listed below in Output is a UNC path. Maybe this is the cause?Output
The text was updated successfully, but these errors were encountered: