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
When I'm working with a project I like to have a venv folder that I generate in the following way.
python -m venv venv
This gives me the possibility to easily access the installed libraries if needed.
I recently noticed that even if I activate the environment. source venv/bin/activate. install something and then deactivate the environment the installed package is still there when you view pip list. So is pyenv incompatible with the usage of python -m venv?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When I'm working with a project I like to have a venv folder that I generate in the following way.
This gives me the possibility to easily access the installed libraries if needed.
I recently noticed that even if I activate the environment.
source venv/bin/activate
. install something and then deactivate the environment the installed package is still there when you viewpip list
. So is pyenv incompatible with the usage ofpython -m venv
?Beta Was this translation helpful? Give feedback.
All reactions