Skip to content
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

[Ops] Virtualenv and requirements #2

Open
matiboy opened this issue Mar 22, 2017 · 1 comment
Open

[Ops] Virtualenv and requirements #2

matiboy opened this issue Mar 22, 2017 · 1 comment

Comments

@matiboy
Copy link

matiboy commented Mar 22, 2017

What is a virtualenv. What are the main advantages of using a virtualenv for your project.
Create a requirements file that will allow all dependencies to be installed for your project

@ai550
Copy link

ai550 commented Mar 24, 2017

Virtualenv is a tool that allows to manage dependencies across the project in a consistent manner. In other words, if there are some specific packages that are needed, you can create a virtual environment and place those versioned packages there.

Main advantage is separation of projects' ecosystems. If I were to install packages globally then I would have some hard time maintaining different projects on my local machine, mainly due to some packages with specific version being used across all of my projects.

requirements.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants