<p>Each Galaxy tool uses its own (typically conda-based) environment, which will normally not use the same python as Galaxy itself (note that Galaxy can run under python 3). An example of this is deepTools, which is python 3 only but will happily run under a python 2 Galaxy since conda is being used to create a python 3 environment for it. It's best to distribute your tool via bioconda and then Galaxy will be easily able to install it.</p>

CC BY-SA 4.0
2020-04-04T22:28:19.707Z
I hope I did it the right way: 1- `conda create ...`, 2-`conda install ...`, etc...
aerijman
CC BY-SA 4.0
2020-04-04T22:30:58.883Z
Yes, though it's best to allow galaxy to make the env for you and put a copy of the wrapper in the toolshed.
Devon Ryan
CC BY-SA 4.0
2020-04-04T16:25:36.397Z
2020-04-04T16:25:36.397Z
Devon Ryan
<p>I am developing a wrapper for a bioinformatics tool written in Python 3.</p>
<p>The native Galaxy-project runs on Python 2.7.</p>
<p>How can I run the tool that requires <code>python3</code> in a <code>galaxy-project</code> instance?</p>

<python><galaxy>
Run a tool with python>=3.6 on a galaxy-project instance that runs on python2.7
# Run a tool with python>=3.6 on a galaxy-project instance that runs on python2.7

(Asked by: username_0 on 2020-04-03)

I am developing a wrapper for a bioinformatics tool written in Python 3.

The native Galaxy-project runs on Python 2.7.

How can I run the tool that requires `python3` in a `galaxy-project` instance?

**Tags:** python, galaxy

---

## 1 answers

### Answer by username_1 on 2020-04-04. Score: 2 | Accepted answer

Each Galaxy tool uses its own (typically conda-based) environment, which will normally not use the same python as Galaxy itself (note that Galaxy can run under python 3). An example of this is deepTools, which is python 3 only but will happily run under a python 2 Galaxy since conda is being used to create a python 3 environment for it. It's best to distribute your tool via bioconda and then Galaxy will be easily able to install it.

> **Comments:**
> **username_0**: I hope I did it the right way: 1- `conda create ...`, 2-`conda install ...`, etc...  
> **username_1**: Yes, though it's best to allow galaxy to make the env for you and put a copy of the wrapper in the toolshed.  

---

