-
Notifications
You must be signed in to change notification settings - Fork 2.5k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Add venv as an environment manager option #164
Comments
Good call. various tools auto-discover “venv” and “.venv” - including IDEs like PyCharm and the (wonderful) package manager, Poetry |
We don't use |
Hah I was misunderstanding this thread. I thought it was talking about which directory name to use for a virtualenv if created within project. But I think OP was talking about venv vs virtualenv libraries in stdlib
…________________________________
From: Peter Bull <[email protected]>
Sent: Monday, April 22, 2019 11:26 AM
To: drivendata/cookiecutter-data-science
Cc: Michael Floering; Mention
Subject: Re: [drivendata/cookiecutter-data-science] Use venv instead of virtualenv (#164)
We don't use venv in our projects could one of you (@hangtwenty<https://github.com/hangtwenty> @nickcorona<https://github.com/nickcorona>) point towards a resource with the basics so that it can be implemented with #162<#162>?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#164 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AASO7UHKBMSAT4DHFMARPI3PRX7MNANCNFSM4HHKWR4A>.
|
Yeah, that is what I mean. |
The general advice is to still prefer Update: In most cases, "virtualenv" is still recommended over just "venv". See the https://virtualenv.pypa.io/en/stable/index.html for details, but basically (as I understand it), only the minimum functionality was migrated to venv to enable everyone to get basic native isolated environments without pip-installing anything. So if you can pip-install anything, then you might as well use virtualenv. |
Changing this issue to consider venv in addition_to and not instead of virtualenv. virtualenv is still popularly used and provides a superset of the functionality of venv. However, it may make sense to include venv as an option since it is part of the Python standard library. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
It's the default python virtual environment library now and ships with python 3.
The text was updated successfully, but these errors were encountered: