-
Notifications
You must be signed in to change notification settings - Fork 2
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
python3 venv support #2
Comments
I think the difference in timings stems mostly from the fact that See: $ time python3 -m venv a
real 0m1.085s
user 0m0.964s
sys 0m0.076s
$ time virtualenv --python python3 --no-download b
Already using interpreter /usr/bin/python3
Using base prefix '/usr'
New python executable in /tmp/envs/b/bin/python3
Also creating executable in /tmp/envs/b/bin/python
Installing setuptools, pkg_resources, pip, wheel...done.
real 0m1.326s
user 0m1.224s
sys 0m0.092s
$ time virtualenv --python python3 c
Already using interpreter /usr/bin/python3
Using base prefix '/usr'
New python executable in /tmp/envs/c/bin/python3
Also creating executable in /tmp/envs/c/bin/python
Installing setuptools, pkg_resources, pip, wheel...done.
real 0m2.031s
user 0m1.872s
sys 0m0.148s This not only slows virtualenv creation, but also introduces (sometimes great) variation in create times. Not to mention it doesn't work when the user is offline. OTOH, the downside of Now, regarding the Thank you for this good idea, I'll have a more detailed look. |
Is it possible to use
python3 -m venv
approach when creating virtualenv for python3? It is much faster (0.936s vs 2.464s on my system).I see it is at least not straight-forward to implement, but it would be a nice feature.
P.S. Thanks for this tool, looks like it is the virtualenv manager I was looking for. According to docs it should fit my workflow exactly...
The text was updated successfully, but these errors were encountered: