Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Ive added a setup.py, allowing phylowgs to be installed into site-packages and used on the commandline. phylowgs_evolve, phylowgs_write_results, phylowgs_create_inputs and phylowgs_parse_cnvs are now on the command line after running setup.py. Note that some files had to be moved. Also, evolve expects phylowgs_mh (not mh) to be on the path. The easiest is to install using conda (recipe included in pull request),
Then your users can
And use phylowgs_evolve without any other setup. To get that to work you have to change the git_rev in meta.yaml to a git revision after this pull request,
conda build phylowgson a general linux, and upload to anaconda.org using the command it spits out at the end of the build.