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

Dependency management #211

Open
afeena opened this issue Nov 13, 2017 · 4 comments
Open

Dependency management #211

afeena opened this issue Nov 13, 2017 · 4 comments

Comments

@afeena
Copy link
Collaborator

afeena commented Nov 13, 2017

New major versions of libraries can broke the build. I think of using pipenv for dependency management, but maybe there is a better way. Topic for discussion

@glaslos
Copy link
Member

glaslos commented Nov 13, 2017

You can also set a required version in the requirements.txt: youpackage==1.0.0

@afeena
Copy link
Collaborator Author

afeena commented Nov 14, 2017

@glaslos Yeah, you're right, it is the easiest way :)

@viskey98
Copy link
Collaborator

viskey98 commented Mar 21, 2018

@afeena I think pipenv would be a good way to implement both dependency management as well as creating a virtual environment for the dependencies. I think we can implement this on SNARE's side as well, what's your opinion?

@xandfury
Copy link
Member

This might be a good opportunity to explore tox as well. tox can check multiple environments and can be integrated with travis. See here

This is like automating what @afeena did, for every pull request.

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

4 participants