Included venv instructions and added venv/ to .gitignore #126
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, running
pip3 install -r requirements.txt
outside of a virtual environment will install packages for the entire system. This is bad, since different projects may require conflicting versions of the same packages. The best practice is to use some kind of virtual environment (this feature typically comes preinstalled with most distributions, so all you really need to do is run a simple command to set it up) and install the packages inside that venv.This also makes it much easier to contribute for anyone who's already familiar with using a venv.
Note that this PR will create a merge conflict with #125 because they both change the contents of the README.md file. I suggest merging this PR first, and then I'll rebase and force-push my config branch for the other PR - that way all you'll need to do is just merge them both.