On Mon, Nov 17, 2014 at 7:23 PM, John Chilton jmchil...@gmail.com wrote:
Ummm... I think it is that the VM started shipping with an
incompatible paramkio.
[...]
Anyway - planemo's TravisCI integration tests Galaxy in a virtualenv
and it works fine [...]
That's a useful workaround, but a
Oops forgot to cc the list.
On Nov 18, 2014 7:26 AM, John Chilton jmchil...@gmail.com wrote:
I will admit to not actually understanding Galaxy's dependency management
but I think virtualenv is exactly the advice people who do understand it
give
On Nov 18, 2014 7:26 AM, John Chilton jmchil...@gmail.com wrote:
I will admit to not actually understanding Galaxy's dependency management
but I think virtualenv is exactly the advice people who do understand it
give
http://dev.list.galaxyproject.org/Local-installation-problem-td4662627.html.
On Tue, Nov 18, 2014 at 1:24 PM, Peter Cock p.j.a.c...@googlemail.com wrote:
On Nov 18, 2014 7:26 AM, John Chilton jmchil...@gmail.com wrote:
I will admit to not actually understanding Galaxy's dependency management
but I think virtualenv is exactly the advice people who do understand it
give
Peter,
Unless you've made modifications to Galaxy that depend on external
libraries, switching to a virtualenv for the server itself should be
pretty safe. Tools themselves can still run without using the/any
virtualenv, if desired.
--nate
On Tue, Nov 18, 2014 at 8:24 AM, Peter Cock
On Tue, Nov 18, 2014 at 5:51 PM, Nate Coraor n...@bx.psu.edu wrote:
Peter,
Unless you've made modifications to Galaxy that depend on external
libraries, switching to a virtualenv for the server itself should be
pretty safe. Tools themselves can still run without using the/any
virtualenv, if
I have had the same issue. A little debugging here:
https://travis-ci.org/saketkc/galaxy_tools/builds/41209515#L84
I first thought that there was a conflict with system installed
paramiko, but it is not:
https://travis-ci.org/saketkc/galaxy_tools/builds/41210153#L60
A clean install of
Ummm... I think it is that the VM started shipping with an
incompatible paramkio. Saket I think you were using -m like it were
-c?
python -m import string # what you had
/usr/bin/python: No module named import string
python -c import string
python -m string
Anyway - planemo's TravisCI
On 17 November 2014 11:23, John Chilton jmchil...@gmail.com wrote:
Ummm... I think it is that the VM started shipping with an
incompatible paramkio. Saket I think you were using -m like it were
-c?
python -m import string # what you had
/usr/bin/python: No module named import string
python
