4 ms·
As I said, a venv is nothing more than a directory + PATH setup. OS already have a dedicated one (in fact, sometimes several). The problem is not that the separ
by BiteCode_dev 5y ago
As I said, a venv is nothing more than a directory + PATH setup. OS already have a dedicated one (in fact, sometimes several). The problem is not that the separation does not exist, the problem is that pip is using the OS real estate.
Creating a new-new separate directory using virtualenv is not going to do anything, just add one more dir to the mix.