Start documenting for non-anaconda users #2
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.
I wanted to run these tools, but I am not an Anaconda user.
I adapted
requirements.txt
to thepip
format, creating the newpip-requirements.txt
. By way of crude documentation, I moved the non-python dependencies to the bottom of this new file, commented out. I didn't actually need to install any of the non-python dependencies, but, then, over time, I may have already installed many of them. So, for a "cleaner" system, there may still be things people need to install. Of course, documenting that part of the process will be much more complicated than it is for Anaconda users.I tried to explain it all in a new section of
README.md
.I tested it by running the three demo commands in
README.md
and got no errors, although I didn't pay much attention to what was actually retrieved.