Thanks John, On Mon, Jan 25, 2016 at 3:29 PM, John Chilton <jmchil...@gmail.com> wrote: > The script generated to call Galaxy is here: > > https://github.com/galaxyproject/galaxy/blob/dev/lib/galaxy/datatypes/metadata.py#L838 > > The job template stuff that setups of the environment the job runs in is here: > > https://github.com/galaxyproject/galaxy/blob/dev/lib/galaxy/jobs/runners/util/job_script/DEFAULT_JOB_FILE_TEMPLATE.sh#L17 > > This second file changes in a large way with 16.01 which ditches eggs > for virtual environments and wheels.
We were trying with v15.10 (I think), but since its late January 2016, can we expect a v16.01 release shortly? That might be quite timely as we're not going to be working on our new VM server and its cluster integration till next week... > We don't explicitly support running different versions of Python on > the worker and handler it seems - but I have seen it work before. You > could probably hack up DEFAULT_JOB_FILE_TEMPLATE.sh to point at a > different instance of Galaxy for your version. I'd hope there was > something easier though. So there should probably be a note on the cluster wiki page about recommending having the same version of Python on the cluster nodes and Galaxy sever? https://wiki.galaxyproject.org/Admin/Config/Performance/Cluster Peter ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
