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

Re-re-visit how Galaxy modules are imported. #56

merged 3 commits into from Jan 13, 2015


None yet
1 participant
Copy link

jmchilton commented Jan 13, 2015

Should prevent Galaxy from failing to load if planemo's virtual environment is not deactivated. Eliminates some of the terrible hacks related to de-activating planemo's virutalenv before starting Galaxy (though admittedly introduces its own terrible hack of planemo's runtime sys.path in the CLI load point).

Should close #50 and #55 and is a better response to #47.

jmchilton added some commits Jan 13, 2015

Restructure how galaxy submodules are imported.
Hack planemo's sys.path instead of essentially hacking externally so that Planemo's variant of galaxy modules can never affect external Galaxy calls.
Eliminate hacking of planemo virtualenv at runtime...
... no longer needed because Planemo's PYTHONPATH doesn't need to conflict with Galaxy's - planemo adds the proper modules at runtime not prior to execution.
Improvements to --install_galaxy.
1) Make implicit dependency on virtualenv optional.
2) Don't run - this is done inside of now.

jmchilton added a commit that referenced this pull request Jan 13, 2015

Merge pull request #56 from galaxyproject/restructure_galaxy
Re-re-visit how Galaxy modules are imported.

@jmchilton jmchilton merged commit 4250874 into master Jan 13, 2015

1 check was pending

continuous-integration/travis-ci The Travis CI build is in progress

jmchilton added a commit that referenced this pull request Jan 13, 2015

Eliminate scary warning about planemo's virtualenv...
... I believe this is no longer a problem after pull request #56.

@jmchilton jmchilton deleted the restructure_galaxy branch Mar 3, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment