How do I remove/delete a virtualenv?How to remove a virtualenv created by “pipenv run”remove virtual environment created with venv in python3rmvirtualenv <name> does not remove a envHow to completely remove vitualenv?How to merge two dictionaries in a single expression?How do I check if a list is empty?How do I check whether a file exists without exceptions?How can I safely create a nested directory in Python?How do I sort a dictionary by value?How to leave/exit/deactivate a Python virtualenvUse different Python version with virtualenvHow do I list all files of a directory?Delete a file or folderUsing Python 3 in virtualenv
Ambiguity in the definition of entropy
How does a predictive coding aid in lossless compression?
Can a virus destroy the BIOS of a modern computer?
How to tell a function to use the default argument values?
How can I determine if the org that I'm currently connected to is a scratch org?
Could the museum Saturn V's be refitted for one more flight?
How badly should I try to prevent a user from XSSing themselves?
I would say: "You are another teacher", but she is a woman and I am a man
Should I cover my bicycle overnight while bikepacking?
What reasons are there for a Capitalist to oppose a 100% inheritance tax?
Avoiding direct proof while writing proof by induction
How to prevent "they're falling in love" trope
Can compressed videos be decoded back to their uncompresed original format?
How do I deal with an unproductive colleague in a small company?
Do UK voters know if their MP will be the Speaker of the House?
Mathematica command that allows it to read my intentions
Cursor Replacement for Newbies
How seriously should I take size and weight limits of hand luggage?
Why are the 737's rear doors unusable in a water landing?
Am I breaking OOP practice with this architecture?
Plagiarism or not?
If human space travel is limited by the G force vulnerability, is there a way to counter G forces?
What mechanic is there to disable a threat instead of killing it?
What is a romance in Latin?
How do I remove/delete a virtualenv?
How to remove a virtualenv created by “pipenv run”remove virtual environment created with venv in python3rmvirtualenv <name> does not remove a envHow to completely remove vitualenv?How to merge two dictionaries in a single expression?How do I check if a list is empty?How do I check whether a file exists without exceptions?How can I safely create a nested directory in Python?How do I sort a dictionary by value?How to leave/exit/deactivate a Python virtualenvUse different Python version with virtualenvHow do I list all files of a directory?Delete a file or folderUsing Python 3 in virtualenv
I created an environment with the following command: virtualenv venv --distribute
I cannot remove it with the following command: rmvirtualenv venv
-
This is part of virtualenvwrapper as mentioned in answer below for virtualenvwrapper
I do an ls
on my current directory and I still see venv
The only way I can remove it seems to be: sudo rm -rf venv
Note that the environment is not active. I'm running Ubuntu 11.10. Any ideas? I've tried rebooting my system to no avail.
python virtualenv virtualenvwrapper virtualenv-commands
add a comment |
I created an environment with the following command: virtualenv venv --distribute
I cannot remove it with the following command: rmvirtualenv venv
-
This is part of virtualenvwrapper as mentioned in answer below for virtualenvwrapper
I do an ls
on my current directory and I still see venv
The only way I can remove it seems to be: sudo rm -rf venv
Note that the environment is not active. I'm running Ubuntu 11.10. Any ideas? I've tried rebooting my system to no avail.
python virtualenv virtualenvwrapper virtualenv-commands
2
What's your problem just removing it (withoutsudo
)? And why do you think a reboot would help?
– Benjamin Bannier
Jun 12 '12 at 21:56
9
Just remove the directory.
– nathancahill
Jun 12 '12 at 21:57
honk: sudo rmvirtualenv venv is not a valid command. Not sure why I thought a reboot would help. I'm fairly new, to be a honest.
– sudostack
Jun 12 '12 at 21:57
20
Note thatrmvirtualenv
comes with virtualenvwrapper. You need that installed to make it work.
– skytreader
Apr 7 '13 at 4:34
3
Note that you can also remove all currently installed packages, but keep the virtual environment itself if you have virtualenvwrapper installed:$ virtualenv --clear path_to_my_venv
. I use this from time to time to make sure I don't have anything manually installed, like an old dependency no longer inrequirements.txt
.
– Taylor Edmiston
Apr 15 '15 at 16:08
add a comment |
I created an environment with the following command: virtualenv venv --distribute
I cannot remove it with the following command: rmvirtualenv venv
-
This is part of virtualenvwrapper as mentioned in answer below for virtualenvwrapper
I do an ls
on my current directory and I still see venv
The only way I can remove it seems to be: sudo rm -rf venv
Note that the environment is not active. I'm running Ubuntu 11.10. Any ideas? I've tried rebooting my system to no avail.
python virtualenv virtualenvwrapper virtualenv-commands
I created an environment with the following command: virtualenv venv --distribute
I cannot remove it with the following command: rmvirtualenv venv
-
This is part of virtualenvwrapper as mentioned in answer below for virtualenvwrapper
I do an ls
on my current directory and I still see venv
The only way I can remove it seems to be: sudo rm -rf venv
Note that the environment is not active. I'm running Ubuntu 11.10. Any ideas? I've tried rebooting my system to no avail.
python virtualenv virtualenvwrapper virtualenv-commands
python virtualenv virtualenvwrapper virtualenv-commands
edited Jun 22 '17 at 2:33
Abhijeet
5,29714964
5,29714964
asked Jun 12 '12 at 21:54
sudostacksudostack
1,87721313
1,87721313
2
What's your problem just removing it (withoutsudo
)? And why do you think a reboot would help?
– Benjamin Bannier
Jun 12 '12 at 21:56
9
Just remove the directory.
– nathancahill
Jun 12 '12 at 21:57
honk: sudo rmvirtualenv venv is not a valid command. Not sure why I thought a reboot would help. I'm fairly new, to be a honest.
– sudostack
Jun 12 '12 at 21:57
20
Note thatrmvirtualenv
comes with virtualenvwrapper. You need that installed to make it work.
– skytreader
Apr 7 '13 at 4:34
3
Note that you can also remove all currently installed packages, but keep the virtual environment itself if you have virtualenvwrapper installed:$ virtualenv --clear path_to_my_venv
. I use this from time to time to make sure I don't have anything manually installed, like an old dependency no longer inrequirements.txt
.
– Taylor Edmiston
Apr 15 '15 at 16:08
add a comment |
2
What's your problem just removing it (withoutsudo
)? And why do you think a reboot would help?
– Benjamin Bannier
Jun 12 '12 at 21:56
9
Just remove the directory.
– nathancahill
Jun 12 '12 at 21:57
honk: sudo rmvirtualenv venv is not a valid command. Not sure why I thought a reboot would help. I'm fairly new, to be a honest.
– sudostack
Jun 12 '12 at 21:57
20
Note thatrmvirtualenv
comes with virtualenvwrapper. You need that installed to make it work.
– skytreader
Apr 7 '13 at 4:34
3
Note that you can also remove all currently installed packages, but keep the virtual environment itself if you have virtualenvwrapper installed:$ virtualenv --clear path_to_my_venv
. I use this from time to time to make sure I don't have anything manually installed, like an old dependency no longer inrequirements.txt
.
– Taylor Edmiston
Apr 15 '15 at 16:08
2
2
What's your problem just removing it (without
sudo
)? And why do you think a reboot would help?– Benjamin Bannier
Jun 12 '12 at 21:56
What's your problem just removing it (without
sudo
)? And why do you think a reboot would help?– Benjamin Bannier
Jun 12 '12 at 21:56
9
9
Just remove the directory.
– nathancahill
Jun 12 '12 at 21:57
Just remove the directory.
– nathancahill
Jun 12 '12 at 21:57
honk: sudo rmvirtualenv venv is not a valid command. Not sure why I thought a reboot would help. I'm fairly new, to be a honest.
– sudostack
Jun 12 '12 at 21:57
honk: sudo rmvirtualenv venv is not a valid command. Not sure why I thought a reboot would help. I'm fairly new, to be a honest.
– sudostack
Jun 12 '12 at 21:57
20
20
Note that
rmvirtualenv
comes with virtualenvwrapper. You need that installed to make it work.– skytreader
Apr 7 '13 at 4:34
Note that
rmvirtualenv
comes with virtualenvwrapper. You need that installed to make it work.– skytreader
Apr 7 '13 at 4:34
3
3
Note that you can also remove all currently installed packages, but keep the virtual environment itself if you have virtualenvwrapper installed:
$ virtualenv --clear path_to_my_venv
. I use this from time to time to make sure I don't have anything manually installed, like an old dependency no longer in requirements.txt
.– Taylor Edmiston
Apr 15 '15 at 16:08
Note that you can also remove all currently installed packages, but keep the virtual environment itself if you have virtualenvwrapper installed:
$ virtualenv --clear path_to_my_venv
. I use this from time to time to make sure I don't have anything manually installed, like an old dependency no longer in requirements.txt
.– Taylor Edmiston
Apr 15 '15 at 16:08
add a comment |
13 Answers
13
active
oldest
votes
That's it! There is no command for deleting your virtual environment. Simply deactivate it and rid your application of its artifacts by recursively removing it.
12
It's worth noting that if you are using pip to install dependencies, you might want to pip freeze a dependency list and keep at the top level directory. If you later choose to deploy your application, you won't have a bit of trouble.
– Thomas Anthony
Jun 12 '12 at 22:18
7
Why is this accepted and with this much votes, when the correct answer is just bellow? Maybe this was for an older version of virtualenvwarpper
– jsbueno
Aug 28 '15 at 15:11
6
@jsbueno He was using virtualenv, not virtualenvwrapper (they are not the same program). At the time, virtualenv provided no interface for clean up; you had to do it yourself.
– Thomas Anthony
Jan 23 '16 at 2:12
If you've created a virtualenv in a git repo (and the files are not ignored):git clean -dffx
– Rex Hardin
Feb 22 '18 at 3:35
add a comment |
Just to echo what @skytreader had previously commented, rmvirtualenv
is a command provided by virtualenvwrapper
, not virtualenv
. Maybe you didn't have virtualenvwrapper
installed?
See VirtualEnvWrapper Command Reference for more details.
add a comment |
Use rmvirtualenv
Remove an environment, in the $WORKON_HOME
.
Syntax:
rmvirtualenv ENVNAME
You must use deactivate before removing the current environment.
$ rmvirtualenv my_env
Reference: http://virtualenvwrapper.readthedocs.io/en/latest/command_ref.html
4
Your answer is easier and better. haha
– Joab Mendes
Nov 5 '16 at 0:33
2
there is eventab
completion support for this!
– muon
Feb 8 '17 at 19:47
8
Note that this answer is wrong as the OP never said that they hadvirtualenvwrapper
– KevinDTimm
Jun 13 '17 at 21:20
add a comment |
You can remove all the dependencies by recursively uninstalling all of them and then delete the venv.
Edit including Isaac Turner commentary
source venv/bin/activate
pip freeze > requirements.txt
pip uninstall -r requirements.txt -y
deactivate
rm -r venv/
1
I think you're missing adeactivate
before therm -r venv/
– Isaac Turner
Dec 7 '16 at 15:17
And critically only do this if you are not sharing the system'spip
! (Otherwise you will uninstall all of your system packages.)
– orome
Jan 9 '18 at 17:29
add a comment |
Simply remove the virtual environment from the system.There's no special command for it
rm -rf venv
add a comment |
from virtualenv's official document https://virtualenv.pypa.io/en/stable/userguide/
Removing an Environment
Removing a virtual environment is simply done by deactivating it and deleting the environment folder with all its contents:
(ENV)$ deactivate
$ rm -r /path/to/ENV
with administrator rights
– Sébastien Wieckowski
Sep 21 '18 at 15:11
add a comment |
I used pyenv uninstall my_virt_env_name
to delete the virual environment.
Note: I'm using pyenv-virtualenv installed through the install script.
add a comment |
if you are windows user, then it's in C:Usersyour_user_nameEnvs. You can delete it from there.
Also try in command prompt rmvirtualenv environment name.
I tried with command prompt so it said deleted but it was still existed. So i manually delete it.
Actually this isn't true. The location of the virtual environment really depends on where you execute thevirtualenv
command. E.g.:C:>virtualenv my_awesome_venv
will create the virtual environment inC:my_awesome_venv
.
– Felix
Apr 1 '17 at 11:55
i was talking about the virtualwrapper. My mistake
– jahmed31
Apr 1 '17 at 12:11
you were right, I had the same problem
– Egon Stetmann.
Jul 5 '17 at 2:39
add a comment |
The following command works for me.
rm -rf /path/to/virtualenv
add a comment |
deactivate
is the command you are looking for. Like what has already been said, there is no command for deleting your virtual environment. Simply deactivate it!
add a comment |
If you are a Windows user and you are using conda to manage the environment in Anaconda prompt, you can do the following:
Make sure you deactivate the virtual environment or restart Anaconda Prompt. Use the following command to remove virtual environment:
$ conda env remove --name $MyEnvironmentName
Alternatively, you can go to the C:UsersUSERNAMEAppDataLocalContinuumanaconda3envsMYENVIRONMENTNAME (that's the default file path) and delete the folder manually.
add a comment |
step 1: delete virtualenv virtualenvwrapper by copy and paste the following command below:
$ sudo pip uninstall virtualenv virtualenvwrapper
step 2: go to .bashrc and delete all virtualenv and virtualenvwrapper
open terminal:
$ sudo nano .bashrc
scroll down and you will see the code bellow then delete it.
# virtualenv and virtualenvwrapper
export WORKON_HOME=$HOME/.virtualenvs
export VIRTUALENVWRAPPER_PYTHON=/usr/bin/python3
source /usr/local/bin/virtualenvwrapper.sh
next, source the .bashrc:
$ source ~/.bashrc
FINAL steps: without terminal/shell go to /home and find .virtualenv
(I forgot the name so if your find similar to .virtualenv
or .venv
just delete it. That will work.
add a comment |
so, I have done a bit of google, but none of the answers were satisfactory.
But accidentally , while scrolling through man pages of pip(utility to install python supported packages - virtualenv is one of them) , it was documented to use of "uninstall" keyword with pip, below is exact output straight from my terminal
indresh-VBX] **$ sudo pip uninstall virtualenv**
The directory '/home/indresh/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Uninstalling virtualenv-15.1.0:
/usr/bin/virtualenv
/usr/local/bin/virtualenv
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/DESCRIPTION.rst
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/INSTALLER
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/METADATA
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/RECORD
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/WHEEL
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/entry_points.txt
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/metadata.json
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/top_level.txt
/usr/local/lib/python2.7/dist-packages/virtualenv.py
/usr/local/lib/python2.7/dist-packages/virtualenv.pyc
/usr/local/lib/python2.7/dist-packages/virtuakmr.ndrsh@gmail.comlenv_support/__init__.py
/usr/local/lib/python2.7/dist-packages/virtualenv_support/__init__.pyc
/usr/local/lib/python2.7/dist-packages/virtualenv_support/argparse-1.4.0-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/pip-9.0.1-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/setuptools-28.8.0-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/wheel-0.29.0-py2.py3-none-any.whl
Proceed (y/n)? y
Successfully uninstalled virtualenv-15.1.0
The directory '/home/indresh/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
--------------------------------
2
The OP's question is how to remove a virtualenv, not how to uninstall the virtualenv package.
– snakecharmerb
Jun 23 '17 at 6:07
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f11005457%2fhow-do-i-remove-delete-a-virtualenv%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
13 Answers
13
active
oldest
votes
13 Answers
13
active
oldest
votes
active
oldest
votes
active
oldest
votes
That's it! There is no command for deleting your virtual environment. Simply deactivate it and rid your application of its artifacts by recursively removing it.
12
It's worth noting that if you are using pip to install dependencies, you might want to pip freeze a dependency list and keep at the top level directory. If you later choose to deploy your application, you won't have a bit of trouble.
– Thomas Anthony
Jun 12 '12 at 22:18
7
Why is this accepted and with this much votes, when the correct answer is just bellow? Maybe this was for an older version of virtualenvwarpper
– jsbueno
Aug 28 '15 at 15:11
6
@jsbueno He was using virtualenv, not virtualenvwrapper (they are not the same program). At the time, virtualenv provided no interface for clean up; you had to do it yourself.
– Thomas Anthony
Jan 23 '16 at 2:12
If you've created a virtualenv in a git repo (and the files are not ignored):git clean -dffx
– Rex Hardin
Feb 22 '18 at 3:35
add a comment |
That's it! There is no command for deleting your virtual environment. Simply deactivate it and rid your application of its artifacts by recursively removing it.
12
It's worth noting that if you are using pip to install dependencies, you might want to pip freeze a dependency list and keep at the top level directory. If you later choose to deploy your application, you won't have a bit of trouble.
– Thomas Anthony
Jun 12 '12 at 22:18
7
Why is this accepted and with this much votes, when the correct answer is just bellow? Maybe this was for an older version of virtualenvwarpper
– jsbueno
Aug 28 '15 at 15:11
6
@jsbueno He was using virtualenv, not virtualenvwrapper (they are not the same program). At the time, virtualenv provided no interface for clean up; you had to do it yourself.
– Thomas Anthony
Jan 23 '16 at 2:12
If you've created a virtualenv in a git repo (and the files are not ignored):git clean -dffx
– Rex Hardin
Feb 22 '18 at 3:35
add a comment |
That's it! There is no command for deleting your virtual environment. Simply deactivate it and rid your application of its artifacts by recursively removing it.
That's it! There is no command for deleting your virtual environment. Simply deactivate it and rid your application of its artifacts by recursively removing it.
edited Nov 11 '17 at 0:29
garrettmac
4,90112939
4,90112939
answered Jun 12 '12 at 21:58
Thomas AnthonyThomas Anthony
3,2051107
3,2051107
12
It's worth noting that if you are using pip to install dependencies, you might want to pip freeze a dependency list and keep at the top level directory. If you later choose to deploy your application, you won't have a bit of trouble.
– Thomas Anthony
Jun 12 '12 at 22:18
7
Why is this accepted and with this much votes, when the correct answer is just bellow? Maybe this was for an older version of virtualenvwarpper
– jsbueno
Aug 28 '15 at 15:11
6
@jsbueno He was using virtualenv, not virtualenvwrapper (they are not the same program). At the time, virtualenv provided no interface for clean up; you had to do it yourself.
– Thomas Anthony
Jan 23 '16 at 2:12
If you've created a virtualenv in a git repo (and the files are not ignored):git clean -dffx
– Rex Hardin
Feb 22 '18 at 3:35
add a comment |
12
It's worth noting that if you are using pip to install dependencies, you might want to pip freeze a dependency list and keep at the top level directory. If you later choose to deploy your application, you won't have a bit of trouble.
– Thomas Anthony
Jun 12 '12 at 22:18
7
Why is this accepted and with this much votes, when the correct answer is just bellow? Maybe this was for an older version of virtualenvwarpper
– jsbueno
Aug 28 '15 at 15:11
6
@jsbueno He was using virtualenv, not virtualenvwrapper (they are not the same program). At the time, virtualenv provided no interface for clean up; you had to do it yourself.
– Thomas Anthony
Jan 23 '16 at 2:12
If you've created a virtualenv in a git repo (and the files are not ignored):git clean -dffx
– Rex Hardin
Feb 22 '18 at 3:35
12
12
It's worth noting that if you are using pip to install dependencies, you might want to pip freeze a dependency list and keep at the top level directory. If you later choose to deploy your application, you won't have a bit of trouble.
– Thomas Anthony
Jun 12 '12 at 22:18
It's worth noting that if you are using pip to install dependencies, you might want to pip freeze a dependency list and keep at the top level directory. If you later choose to deploy your application, you won't have a bit of trouble.
– Thomas Anthony
Jun 12 '12 at 22:18
7
7
Why is this accepted and with this much votes, when the correct answer is just bellow? Maybe this was for an older version of virtualenvwarpper
– jsbueno
Aug 28 '15 at 15:11
Why is this accepted and with this much votes, when the correct answer is just bellow? Maybe this was for an older version of virtualenvwarpper
– jsbueno
Aug 28 '15 at 15:11
6
6
@jsbueno He was using virtualenv, not virtualenvwrapper (they are not the same program). At the time, virtualenv provided no interface for clean up; you had to do it yourself.
– Thomas Anthony
Jan 23 '16 at 2:12
@jsbueno He was using virtualenv, not virtualenvwrapper (they are not the same program). At the time, virtualenv provided no interface for clean up; you had to do it yourself.
– Thomas Anthony
Jan 23 '16 at 2:12
If you've created a virtualenv in a git repo (and the files are not ignored):
git clean -dffx
– Rex Hardin
Feb 22 '18 at 3:35
If you've created a virtualenv in a git repo (and the files are not ignored):
git clean -dffx
– Rex Hardin
Feb 22 '18 at 3:35
add a comment |
Just to echo what @skytreader had previously commented, rmvirtualenv
is a command provided by virtualenvwrapper
, not virtualenv
. Maybe you didn't have virtualenvwrapper
installed?
See VirtualEnvWrapper Command Reference for more details.
add a comment |
Just to echo what @skytreader had previously commented, rmvirtualenv
is a command provided by virtualenvwrapper
, not virtualenv
. Maybe you didn't have virtualenvwrapper
installed?
See VirtualEnvWrapper Command Reference for more details.
add a comment |
Just to echo what @skytreader had previously commented, rmvirtualenv
is a command provided by virtualenvwrapper
, not virtualenv
. Maybe you didn't have virtualenvwrapper
installed?
See VirtualEnvWrapper Command Reference for more details.
Just to echo what @skytreader had previously commented, rmvirtualenv
is a command provided by virtualenvwrapper
, not virtualenv
. Maybe you didn't have virtualenvwrapper
installed?
See VirtualEnvWrapper Command Reference for more details.
answered Sep 4 '13 at 22:23
DevyDevy
5,19323846
5,19323846
add a comment |
add a comment |
Use rmvirtualenv
Remove an environment, in the $WORKON_HOME
.
Syntax:
rmvirtualenv ENVNAME
You must use deactivate before removing the current environment.
$ rmvirtualenv my_env
Reference: http://virtualenvwrapper.readthedocs.io/en/latest/command_ref.html
4
Your answer is easier and better. haha
– Joab Mendes
Nov 5 '16 at 0:33
2
there is eventab
completion support for this!
– muon
Feb 8 '17 at 19:47
8
Note that this answer is wrong as the OP never said that they hadvirtualenvwrapper
– KevinDTimm
Jun 13 '17 at 21:20
add a comment |
Use rmvirtualenv
Remove an environment, in the $WORKON_HOME
.
Syntax:
rmvirtualenv ENVNAME
You must use deactivate before removing the current environment.
$ rmvirtualenv my_env
Reference: http://virtualenvwrapper.readthedocs.io/en/latest/command_ref.html
4
Your answer is easier and better. haha
– Joab Mendes
Nov 5 '16 at 0:33
2
there is eventab
completion support for this!
– muon
Feb 8 '17 at 19:47
8
Note that this answer is wrong as the OP never said that they hadvirtualenvwrapper
– KevinDTimm
Jun 13 '17 at 21:20
add a comment |
Use rmvirtualenv
Remove an environment, in the $WORKON_HOME
.
Syntax:
rmvirtualenv ENVNAME
You must use deactivate before removing the current environment.
$ rmvirtualenv my_env
Reference: http://virtualenvwrapper.readthedocs.io/en/latest/command_ref.html
Use rmvirtualenv
Remove an environment, in the $WORKON_HOME
.
Syntax:
rmvirtualenv ENVNAME
You must use deactivate before removing the current environment.
$ rmvirtualenv my_env
Reference: http://virtualenvwrapper.readthedocs.io/en/latest/command_ref.html
edited Jun 7 '18 at 4:05
aydow
2,45511127
2,45511127
answered Oct 24 '16 at 5:16
AntoniazziAntoniazzi
89669
89669
4
Your answer is easier and better. haha
– Joab Mendes
Nov 5 '16 at 0:33
2
there is eventab
completion support for this!
– muon
Feb 8 '17 at 19:47
8
Note that this answer is wrong as the OP never said that they hadvirtualenvwrapper
– KevinDTimm
Jun 13 '17 at 21:20
add a comment |
4
Your answer is easier and better. haha
– Joab Mendes
Nov 5 '16 at 0:33
2
there is eventab
completion support for this!
– muon
Feb 8 '17 at 19:47
8
Note that this answer is wrong as the OP never said that they hadvirtualenvwrapper
– KevinDTimm
Jun 13 '17 at 21:20
4
4
Your answer is easier and better. haha
– Joab Mendes
Nov 5 '16 at 0:33
Your answer is easier and better. haha
– Joab Mendes
Nov 5 '16 at 0:33
2
2
there is even
tab
completion support for this!– muon
Feb 8 '17 at 19:47
there is even
tab
completion support for this!– muon
Feb 8 '17 at 19:47
8
8
Note that this answer is wrong as the OP never said that they had
virtualenvwrapper
– KevinDTimm
Jun 13 '17 at 21:20
Note that this answer is wrong as the OP never said that they had
virtualenvwrapper
– KevinDTimm
Jun 13 '17 at 21:20
add a comment |
You can remove all the dependencies by recursively uninstalling all of them and then delete the venv.
Edit including Isaac Turner commentary
source venv/bin/activate
pip freeze > requirements.txt
pip uninstall -r requirements.txt -y
deactivate
rm -r venv/
1
I think you're missing adeactivate
before therm -r venv/
– Isaac Turner
Dec 7 '16 at 15:17
And critically only do this if you are not sharing the system'spip
! (Otherwise you will uninstall all of your system packages.)
– orome
Jan 9 '18 at 17:29
add a comment |
You can remove all the dependencies by recursively uninstalling all of them and then delete the venv.
Edit including Isaac Turner commentary
source venv/bin/activate
pip freeze > requirements.txt
pip uninstall -r requirements.txt -y
deactivate
rm -r venv/
1
I think you're missing adeactivate
before therm -r venv/
– Isaac Turner
Dec 7 '16 at 15:17
And critically only do this if you are not sharing the system'spip
! (Otherwise you will uninstall all of your system packages.)
– orome
Jan 9 '18 at 17:29
add a comment |
You can remove all the dependencies by recursively uninstalling all of them and then delete the venv.
Edit including Isaac Turner commentary
source venv/bin/activate
pip freeze > requirements.txt
pip uninstall -r requirements.txt -y
deactivate
rm -r venv/
You can remove all the dependencies by recursively uninstalling all of them and then delete the venv.
Edit including Isaac Turner commentary
source venv/bin/activate
pip freeze > requirements.txt
pip uninstall -r requirements.txt -y
deactivate
rm -r venv/
edited Apr 21 '17 at 16:34
Antman Slaper Man
16115
16115
answered May 11 '16 at 6:11
Dawn T CherianDawn T Cherian
1,94121224
1,94121224
1
I think you're missing adeactivate
before therm -r venv/
– Isaac Turner
Dec 7 '16 at 15:17
And critically only do this if you are not sharing the system'spip
! (Otherwise you will uninstall all of your system packages.)
– orome
Jan 9 '18 at 17:29
add a comment |
1
I think you're missing adeactivate
before therm -r venv/
– Isaac Turner
Dec 7 '16 at 15:17
And critically only do this if you are not sharing the system'spip
! (Otherwise you will uninstall all of your system packages.)
– orome
Jan 9 '18 at 17:29
1
1
I think you're missing a
deactivate
before the rm -r venv/
– Isaac Turner
Dec 7 '16 at 15:17
I think you're missing a
deactivate
before the rm -r venv/
– Isaac Turner
Dec 7 '16 at 15:17
And critically only do this if you are not sharing the system's
pip
! (Otherwise you will uninstall all of your system packages.)– orome
Jan 9 '18 at 17:29
And critically only do this if you are not sharing the system's
pip
! (Otherwise you will uninstall all of your system packages.)– orome
Jan 9 '18 at 17:29
add a comment |
Simply remove the virtual environment from the system.There's no special command for it
rm -rf venv
add a comment |
Simply remove the virtual environment from the system.There's no special command for it
rm -rf venv
add a comment |
Simply remove the virtual environment from the system.There's no special command for it
rm -rf venv
Simply remove the virtual environment from the system.There's no special command for it
rm -rf venv
answered Sep 21 '16 at 18:16
Naveen AgarwalNaveen Agarwal
42046
42046
add a comment |
add a comment |
from virtualenv's official document https://virtualenv.pypa.io/en/stable/userguide/
Removing an Environment
Removing a virtual environment is simply done by deactivating it and deleting the environment folder with all its contents:
(ENV)$ deactivate
$ rm -r /path/to/ENV
with administrator rights
– Sébastien Wieckowski
Sep 21 '18 at 15:11
add a comment |
from virtualenv's official document https://virtualenv.pypa.io/en/stable/userguide/
Removing an Environment
Removing a virtual environment is simply done by deactivating it and deleting the environment folder with all its contents:
(ENV)$ deactivate
$ rm -r /path/to/ENV
with administrator rights
– Sébastien Wieckowski
Sep 21 '18 at 15:11
add a comment |
from virtualenv's official document https://virtualenv.pypa.io/en/stable/userguide/
Removing an Environment
Removing a virtual environment is simply done by deactivating it and deleting the environment folder with all its contents:
(ENV)$ deactivate
$ rm -r /path/to/ENV
from virtualenv's official document https://virtualenv.pypa.io/en/stable/userguide/
Removing an Environment
Removing a virtual environment is simply done by deactivating it and deleting the environment folder with all its contents:
(ENV)$ deactivate
$ rm -r /path/to/ENV
edited Mar 3 '18 at 12:31
Konrad Borowski
7,38624162
7,38624162
answered Mar 3 '18 at 12:27
N.LeeN.Lee
41849
41849
with administrator rights
– Sébastien Wieckowski
Sep 21 '18 at 15:11
add a comment |
with administrator rights
– Sébastien Wieckowski
Sep 21 '18 at 15:11
with administrator rights
– Sébastien Wieckowski
Sep 21 '18 at 15:11
with administrator rights
– Sébastien Wieckowski
Sep 21 '18 at 15:11
add a comment |
I used pyenv uninstall my_virt_env_name
to delete the virual environment.
Note: I'm using pyenv-virtualenv installed through the install script.
add a comment |
I used pyenv uninstall my_virt_env_name
to delete the virual environment.
Note: I'm using pyenv-virtualenv installed through the install script.
add a comment |
I used pyenv uninstall my_virt_env_name
to delete the virual environment.
Note: I'm using pyenv-virtualenv installed through the install script.
I used pyenv uninstall my_virt_env_name
to delete the virual environment.
Note: I'm using pyenv-virtualenv installed through the install script.
edited Aug 17 '18 at 10:00
answered Dec 19 '17 at 0:32
Ole Henrik SkogstrømOle Henrik Skogstrøm
3,77994271
3,77994271
add a comment |
add a comment |
if you are windows user, then it's in C:Usersyour_user_nameEnvs. You can delete it from there.
Also try in command prompt rmvirtualenv environment name.
I tried with command prompt so it said deleted but it was still existed. So i manually delete it.
Actually this isn't true. The location of the virtual environment really depends on where you execute thevirtualenv
command. E.g.:C:>virtualenv my_awesome_venv
will create the virtual environment inC:my_awesome_venv
.
– Felix
Apr 1 '17 at 11:55
i was talking about the virtualwrapper. My mistake
– jahmed31
Apr 1 '17 at 12:11
you were right, I had the same problem
– Egon Stetmann.
Jul 5 '17 at 2:39
add a comment |
if you are windows user, then it's in C:Usersyour_user_nameEnvs. You can delete it from there.
Also try in command prompt rmvirtualenv environment name.
I tried with command prompt so it said deleted but it was still existed. So i manually delete it.
Actually this isn't true. The location of the virtual environment really depends on where you execute thevirtualenv
command. E.g.:C:>virtualenv my_awesome_venv
will create the virtual environment inC:my_awesome_venv
.
– Felix
Apr 1 '17 at 11:55
i was talking about the virtualwrapper. My mistake
– jahmed31
Apr 1 '17 at 12:11
you were right, I had the same problem
– Egon Stetmann.
Jul 5 '17 at 2:39
add a comment |
if you are windows user, then it's in C:Usersyour_user_nameEnvs. You can delete it from there.
Also try in command prompt rmvirtualenv environment name.
I tried with command prompt so it said deleted but it was still existed. So i manually delete it.
if you are windows user, then it's in C:Usersyour_user_nameEnvs. You can delete it from there.
Also try in command prompt rmvirtualenv environment name.
I tried with command prompt so it said deleted but it was still existed. So i manually delete it.
answered Apr 1 '17 at 11:35
jahmed31jahmed31
211
211
Actually this isn't true. The location of the virtual environment really depends on where you execute thevirtualenv
command. E.g.:C:>virtualenv my_awesome_venv
will create the virtual environment inC:my_awesome_venv
.
– Felix
Apr 1 '17 at 11:55
i was talking about the virtualwrapper. My mistake
– jahmed31
Apr 1 '17 at 12:11
you were right, I had the same problem
– Egon Stetmann.
Jul 5 '17 at 2:39
add a comment |
Actually this isn't true. The location of the virtual environment really depends on where you execute thevirtualenv
command. E.g.:C:>virtualenv my_awesome_venv
will create the virtual environment inC:my_awesome_venv
.
– Felix
Apr 1 '17 at 11:55
i was talking about the virtualwrapper. My mistake
– jahmed31
Apr 1 '17 at 12:11
you were right, I had the same problem
– Egon Stetmann.
Jul 5 '17 at 2:39
Actually this isn't true. The location of the virtual environment really depends on where you execute the
virtualenv
command. E.g.: C:>virtualenv my_awesome_venv
will create the virtual environment in C:my_awesome_venv
.– Felix
Apr 1 '17 at 11:55
Actually this isn't true. The location of the virtual environment really depends on where you execute the
virtualenv
command. E.g.: C:>virtualenv my_awesome_venv
will create the virtual environment in C:my_awesome_venv
.– Felix
Apr 1 '17 at 11:55
i was talking about the virtualwrapper. My mistake
– jahmed31
Apr 1 '17 at 12:11
i was talking about the virtualwrapper. My mistake
– jahmed31
Apr 1 '17 at 12:11
you were right, I had the same problem
– Egon Stetmann.
Jul 5 '17 at 2:39
you were right, I had the same problem
– Egon Stetmann.
Jul 5 '17 at 2:39
add a comment |
The following command works for me.
rm -rf /path/to/virtualenv
add a comment |
The following command works for me.
rm -rf /path/to/virtualenv
add a comment |
The following command works for me.
rm -rf /path/to/virtualenv
The following command works for me.
rm -rf /path/to/virtualenv
answered Oct 25 '18 at 16:58
Ashiq ImranAshiq Imran
16214
16214
add a comment |
add a comment |
deactivate
is the command you are looking for. Like what has already been said, there is no command for deleting your virtual environment. Simply deactivate it!
add a comment |
deactivate
is the command you are looking for. Like what has already been said, there is no command for deleting your virtual environment. Simply deactivate it!
add a comment |
deactivate
is the command you are looking for. Like what has already been said, there is no command for deleting your virtual environment. Simply deactivate it!
deactivate
is the command you are looking for. Like what has already been said, there is no command for deleting your virtual environment. Simply deactivate it!
answered Nov 11 '17 at 0:31
garrettmacgarrettmac
4,90112939
4,90112939
add a comment |
add a comment |
If you are a Windows user and you are using conda to manage the environment in Anaconda prompt, you can do the following:
Make sure you deactivate the virtual environment or restart Anaconda Prompt. Use the following command to remove virtual environment:
$ conda env remove --name $MyEnvironmentName
Alternatively, you can go to the C:UsersUSERNAMEAppDataLocalContinuumanaconda3envsMYENVIRONMENTNAME (that's the default file path) and delete the folder manually.
add a comment |
If you are a Windows user and you are using conda to manage the environment in Anaconda prompt, you can do the following:
Make sure you deactivate the virtual environment or restart Anaconda Prompt. Use the following command to remove virtual environment:
$ conda env remove --name $MyEnvironmentName
Alternatively, you can go to the C:UsersUSERNAMEAppDataLocalContinuumanaconda3envsMYENVIRONMENTNAME (that's the default file path) and delete the folder manually.
add a comment |
If you are a Windows user and you are using conda to manage the environment in Anaconda prompt, you can do the following:
Make sure you deactivate the virtual environment or restart Anaconda Prompt. Use the following command to remove virtual environment:
$ conda env remove --name $MyEnvironmentName
Alternatively, you can go to the C:UsersUSERNAMEAppDataLocalContinuumanaconda3envsMYENVIRONMENTNAME (that's the default file path) and delete the folder manually.
If you are a Windows user and you are using conda to manage the environment in Anaconda prompt, you can do the following:
Make sure you deactivate the virtual environment or restart Anaconda Prompt. Use the following command to remove virtual environment:
$ conda env remove --name $MyEnvironmentName
Alternatively, you can go to the C:UsersUSERNAMEAppDataLocalContinuumanaconda3envsMYENVIRONMENTNAME (that's the default file path) and delete the folder manually.
answered Mar 8 at 22:37
CathyQianCathyQian
14012
14012
add a comment |
add a comment |
step 1: delete virtualenv virtualenvwrapper by copy and paste the following command below:
$ sudo pip uninstall virtualenv virtualenvwrapper
step 2: go to .bashrc and delete all virtualenv and virtualenvwrapper
open terminal:
$ sudo nano .bashrc
scroll down and you will see the code bellow then delete it.
# virtualenv and virtualenvwrapper
export WORKON_HOME=$HOME/.virtualenvs
export VIRTUALENVWRAPPER_PYTHON=/usr/bin/python3
source /usr/local/bin/virtualenvwrapper.sh
next, source the .bashrc:
$ source ~/.bashrc
FINAL steps: without terminal/shell go to /home and find .virtualenv
(I forgot the name so if your find similar to .virtualenv
or .venv
just delete it. That will work.
add a comment |
step 1: delete virtualenv virtualenvwrapper by copy and paste the following command below:
$ sudo pip uninstall virtualenv virtualenvwrapper
step 2: go to .bashrc and delete all virtualenv and virtualenvwrapper
open terminal:
$ sudo nano .bashrc
scroll down and you will see the code bellow then delete it.
# virtualenv and virtualenvwrapper
export WORKON_HOME=$HOME/.virtualenvs
export VIRTUALENVWRAPPER_PYTHON=/usr/bin/python3
source /usr/local/bin/virtualenvwrapper.sh
next, source the .bashrc:
$ source ~/.bashrc
FINAL steps: without terminal/shell go to /home and find .virtualenv
(I forgot the name so if your find similar to .virtualenv
or .venv
just delete it. That will work.
add a comment |
step 1: delete virtualenv virtualenvwrapper by copy and paste the following command below:
$ sudo pip uninstall virtualenv virtualenvwrapper
step 2: go to .bashrc and delete all virtualenv and virtualenvwrapper
open terminal:
$ sudo nano .bashrc
scroll down and you will see the code bellow then delete it.
# virtualenv and virtualenvwrapper
export WORKON_HOME=$HOME/.virtualenvs
export VIRTUALENVWRAPPER_PYTHON=/usr/bin/python3
source /usr/local/bin/virtualenvwrapper.sh
next, source the .bashrc:
$ source ~/.bashrc
FINAL steps: without terminal/shell go to /home and find .virtualenv
(I forgot the name so if your find similar to .virtualenv
or .venv
just delete it. That will work.
step 1: delete virtualenv virtualenvwrapper by copy and paste the following command below:
$ sudo pip uninstall virtualenv virtualenvwrapper
step 2: go to .bashrc and delete all virtualenv and virtualenvwrapper
open terminal:
$ sudo nano .bashrc
scroll down and you will see the code bellow then delete it.
# virtualenv and virtualenvwrapper
export WORKON_HOME=$HOME/.virtualenvs
export VIRTUALENVWRAPPER_PYTHON=/usr/bin/python3
source /usr/local/bin/virtualenvwrapper.sh
next, source the .bashrc:
$ source ~/.bashrc
FINAL steps: without terminal/shell go to /home and find .virtualenv
(I forgot the name so if your find similar to .virtualenv
or .venv
just delete it. That will work.
edited Mar 19 at 18:25
answered Feb 25 at 12:52
Wanz HatedWanz Hated
11
11
add a comment |
add a comment |
so, I have done a bit of google, but none of the answers were satisfactory.
But accidentally , while scrolling through man pages of pip(utility to install python supported packages - virtualenv is one of them) , it was documented to use of "uninstall" keyword with pip, below is exact output straight from my terminal
indresh-VBX] **$ sudo pip uninstall virtualenv**
The directory '/home/indresh/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Uninstalling virtualenv-15.1.0:
/usr/bin/virtualenv
/usr/local/bin/virtualenv
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/DESCRIPTION.rst
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/INSTALLER
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/METADATA
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/RECORD
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/WHEEL
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/entry_points.txt
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/metadata.json
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/top_level.txt
/usr/local/lib/python2.7/dist-packages/virtualenv.py
/usr/local/lib/python2.7/dist-packages/virtualenv.pyc
/usr/local/lib/python2.7/dist-packages/virtuakmr.ndrsh@gmail.comlenv_support/__init__.py
/usr/local/lib/python2.7/dist-packages/virtualenv_support/__init__.pyc
/usr/local/lib/python2.7/dist-packages/virtualenv_support/argparse-1.4.0-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/pip-9.0.1-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/setuptools-28.8.0-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/wheel-0.29.0-py2.py3-none-any.whl
Proceed (y/n)? y
Successfully uninstalled virtualenv-15.1.0
The directory '/home/indresh/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
--------------------------------
2
The OP's question is how to remove a virtualenv, not how to uninstall the virtualenv package.
– snakecharmerb
Jun 23 '17 at 6:07
add a comment |
so, I have done a bit of google, but none of the answers were satisfactory.
But accidentally , while scrolling through man pages of pip(utility to install python supported packages - virtualenv is one of them) , it was documented to use of "uninstall" keyword with pip, below is exact output straight from my terminal
indresh-VBX] **$ sudo pip uninstall virtualenv**
The directory '/home/indresh/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Uninstalling virtualenv-15.1.0:
/usr/bin/virtualenv
/usr/local/bin/virtualenv
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/DESCRIPTION.rst
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/INSTALLER
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/METADATA
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/RECORD
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/WHEEL
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/entry_points.txt
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/metadata.json
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/top_level.txt
/usr/local/lib/python2.7/dist-packages/virtualenv.py
/usr/local/lib/python2.7/dist-packages/virtualenv.pyc
/usr/local/lib/python2.7/dist-packages/virtuakmr.ndrsh@gmail.comlenv_support/__init__.py
/usr/local/lib/python2.7/dist-packages/virtualenv_support/__init__.pyc
/usr/local/lib/python2.7/dist-packages/virtualenv_support/argparse-1.4.0-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/pip-9.0.1-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/setuptools-28.8.0-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/wheel-0.29.0-py2.py3-none-any.whl
Proceed (y/n)? y
Successfully uninstalled virtualenv-15.1.0
The directory '/home/indresh/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
--------------------------------
2
The OP's question is how to remove a virtualenv, not how to uninstall the virtualenv package.
– snakecharmerb
Jun 23 '17 at 6:07
add a comment |
so, I have done a bit of google, but none of the answers were satisfactory.
But accidentally , while scrolling through man pages of pip(utility to install python supported packages - virtualenv is one of them) , it was documented to use of "uninstall" keyword with pip, below is exact output straight from my terminal
indresh-VBX] **$ sudo pip uninstall virtualenv**
The directory '/home/indresh/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Uninstalling virtualenv-15.1.0:
/usr/bin/virtualenv
/usr/local/bin/virtualenv
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/DESCRIPTION.rst
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/INSTALLER
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/METADATA
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/RECORD
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/WHEEL
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/entry_points.txt
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/metadata.json
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/top_level.txt
/usr/local/lib/python2.7/dist-packages/virtualenv.py
/usr/local/lib/python2.7/dist-packages/virtualenv.pyc
/usr/local/lib/python2.7/dist-packages/virtuakmr.ndrsh@gmail.comlenv_support/__init__.py
/usr/local/lib/python2.7/dist-packages/virtualenv_support/__init__.pyc
/usr/local/lib/python2.7/dist-packages/virtualenv_support/argparse-1.4.0-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/pip-9.0.1-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/setuptools-28.8.0-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/wheel-0.29.0-py2.py3-none-any.whl
Proceed (y/n)? y
Successfully uninstalled virtualenv-15.1.0
The directory '/home/indresh/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
--------------------------------
so, I have done a bit of google, but none of the answers were satisfactory.
But accidentally , while scrolling through man pages of pip(utility to install python supported packages - virtualenv is one of them) , it was documented to use of "uninstall" keyword with pip, below is exact output straight from my terminal
indresh-VBX] **$ sudo pip uninstall virtualenv**
The directory '/home/indresh/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Uninstalling virtualenv-15.1.0:
/usr/bin/virtualenv
/usr/local/bin/virtualenv
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/DESCRIPTION.rst
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/INSTALLER
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/METADATA
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/RECORD
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/WHEEL
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/entry_points.txt
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/metadata.json
/usr/local/lib/python2.7/dist-packages/virtualenv-15.1.0.dist-info/top_level.txt
/usr/local/lib/python2.7/dist-packages/virtualenv.py
/usr/local/lib/python2.7/dist-packages/virtualenv.pyc
/usr/local/lib/python2.7/dist-packages/virtuakmr.ndrsh@gmail.comlenv_support/__init__.py
/usr/local/lib/python2.7/dist-packages/virtualenv_support/__init__.pyc
/usr/local/lib/python2.7/dist-packages/virtualenv_support/argparse-1.4.0-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/pip-9.0.1-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/setuptools-28.8.0-py2.py3-none-any.whl
/usr/local/lib/python2.7/dist-packages/virtualenv_support/wheel-0.29.0-py2.py3-none-any.whl
Proceed (y/n)? y
Successfully uninstalled virtualenv-15.1.0
The directory '/home/indresh/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
--------------------------------
edited Jun 23 '17 at 0:32
Rob♦
23.5k125777
23.5k125777
answered Jun 22 '17 at 19:06
Indresh KumarIndresh Kumar
7
7
2
The OP's question is how to remove a virtualenv, not how to uninstall the virtualenv package.
– snakecharmerb
Jun 23 '17 at 6:07
add a comment |
2
The OP's question is how to remove a virtualenv, not how to uninstall the virtualenv package.
– snakecharmerb
Jun 23 '17 at 6:07
2
2
The OP's question is how to remove a virtualenv, not how to uninstall the virtualenv package.
– snakecharmerb
Jun 23 '17 at 6:07
The OP's question is how to remove a virtualenv, not how to uninstall the virtualenv package.
– snakecharmerb
Jun 23 '17 at 6:07
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f11005457%2fhow-do-i-remove-delete-a-virtualenv%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
What's your problem just removing it (without
sudo
)? And why do you think a reboot would help?– Benjamin Bannier
Jun 12 '12 at 21:56
9
Just remove the directory.
– nathancahill
Jun 12 '12 at 21:57
honk: sudo rmvirtualenv venv is not a valid command. Not sure why I thought a reboot would help. I'm fairly new, to be a honest.
– sudostack
Jun 12 '12 at 21:57
20
Note that
rmvirtualenv
comes with virtualenvwrapper. You need that installed to make it work.– skytreader
Apr 7 '13 at 4:34
3
Note that you can also remove all currently installed packages, but keep the virtual environment itself if you have virtualenvwrapper installed:
$ virtualenv --clear path_to_my_venv
. I use this from time to time to make sure I don't have anything manually installed, like an old dependency no longer inrequirements.txt
.– Taylor Edmiston
Apr 15 '15 at 16:08