On Tue, Jan 6, 2015 at 12:23 AM, Peter Cock <p.j.a.cock(a)googlemail.com> wrote:
Are you writing your own tool, or trying to install someone else's?
There are two basic options,
(1) Install Biopython into the default Python used when jobs are
run. Simple, but manual - and you can only have one version.
This is actually what we are still doing on our local Galaxy
since we started before the second option as available.
(2) Install Biopython via the ToolShed, using the dependency
mechanism. This allows multiple versions of Biopython (or any
Python library) to be installed in parallel, and Galaxy does the
setup to ensure the declared dependency is on the Python
path when your script is run. e.g.
declares a dependency on:
(which in turn depends on NumPy etc).
This reminds me, we are overdue to create a Galaxy ToolShed
package for Biopython 1.65, I must do that...