Closed mvdbeek closed 8 years ago
This exception is the one I've been seeing for quite some time now - I don't think it is related to conda.
I'm using VMs provided by the IFB. If I don't install conda everything works fine ... but indeed, it might be related to python-2.7.11 that conda is shipping with. Or other things ... I'm at a loss, but if this works I could easily test our tool repository in travis.
@natefoo added some parameters to Galaxy's scripts to fix this, I need to adapt planemo to them.
Instructions for running Galaxy tools in a conda with planemo here https://github.com/galaxyproject/planemo/commit/9f3957d3552153cd76ec34697e9857be13a24e73, though that is for planemo installed via brew or in a virtualenv.
If for some reason you want to install planemo into a conda environment, then Galaxy needs to already have its virtual environment setup and cannot reuse the same conda environment (planemo depends on galaxy-lib which conflicts with galaxy). So just clone galaxy (dev or release_16.01), run run.sh once, and then call planemo with --galaxy_root.
Does this make sense - are these restrictions fair? If not, we can keep the issue open and try to improve the conda+galaxy+planemo story
What if you've installed planemo via pip?
An expanded summary of the state of planemo, Galaxy, conda:
awesome, thanks @jmchilton , I'll give it a go.
Here planeme test
crashes with the error reported above by @mvdbeek and otherwise I get this error (planemo 0.22.2, via homebrew):
You've placed galaxy-lib in the same Python environment as Galaxy. Galaxy and Planemo must be installed in different environments currently.
Closing this for now, I'll keep working on the galaxy-lib problem - there doesn't seem to be a clean fix.
Not quite sure if this is an issue with conda, galaxy or planemo ...