-
Notifications
You must be signed in to change notification settings - Fork 12
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 requirements file #10
Conversation
Current modules used in all files For easy use with pip install -r --upgrade requirements.txt
Looks good! Thanks for putting this together. |
Can you squash these commits when merging? |
@pahdo I've made it a setting to only allow squash commits when merging a pull request. I generally agree with this approach as it keeps |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also pending conversation here: https://sfbrigade.slack.com/archives/CEL6C4Q49/p1547185246007700 I would say lets hold off merging a tiny bit as we resolve whether we should use Anaconda or pip/virtual env to manage our environments.
See #21 |
Happy to move over to Anaconda as we discussed |
Requirements file so that anyone can get started with the repo by pip installing these packages into their virtual environment
I added the current modules for any package used in all files - Excluding standard python 3.6 packages
You can use
pip install -r --upgrade requirements.txt
from within the base directory to install these packagesPartly addresses issue in #6