2 ms·
it is not really. now it is python3.X -m venv which is still virtualenv but again a different implementation with different bugs
by je42 9y ago
it is not really.
now it is python3.X -m venv
which is still virtualenv but again a different implementation with different bugs