Wrapped the options reference path getter calls with calls to os.path.join #6
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.
Wrapped the options reference path getter calls with calls to os.path.join, in case the path doesn't end in a trailing path separator
I found a small bug when running the test tipp analysis (traceback below), because I had set the REFERENCE environment variable to a path without a trailing slash. This meant that metagenomics.py wasn't able to construct its BLAST paths correctly. The guess easy fix is to add the path separator to REFERENCE, but I wrapped os.path.join calls around the path constructors involving
options().__getattribute__('reference').path + 'some_string'
I don't do many of these pull requests, I hope I got the etiquette right. If not, it's through ignorance, not malice.
The traceback I got was:
Blasting fragments against marker dataset