Hi Wolfgang,
I guess that the conda recipe should be updated to also specify
- python >=3
in the requirements.
Cheers,
Nicola
On 03/11/16 21:04, Wolfgang Maier wrote:
I'm not quite sure if I understand you correctly, but let's see.
The original tool wrapper stated
python3
as a dependency. T
I'm not quite sure if I understand you correctly, but let's see.
The original tool wrapper stated
python3
as a dependency. This did not work with at runtime installation at all
because conda cannot resolve python3 and the requirement got ignored by
Galaxy. I changed the requirement tag now to:
Hi,
can you check the package? The package should have a dependency on
python3, if not the package seems to be broken :(
Ciao,
Bjoern
Am 03.11.2016 um 21:32 schrieb Wolfgang Maier:
> Hi Björn,
>
> Hmm, I guess I should have phrased my question more clearly. What I'm
> trying to do is to get Gal
Hi Björn,
Hmm, I guess I should have phrased my question more clearly. What I'm
trying to do is to get Galaxy to satisfy a missing tool dependency at
*tool runtime* using a bioconda package that is only available for
Python3. I am able to satisfy the dependency *manually* by running:
conda c
Hi Wolfgang,
can you describe step by step what you are trying to do?
A conda package ships it's own python version, you can see this in the
build-string py35_0 for example. So conda can handle all python version
independent of the python version of miniconda.
Cheers,
Bjoern
> Dear all,
>
> I'
Dear all,
I'm still pretty new to conda tool dependencies management and there is
one thing I cannot find documented anywhere:
How can I let conda manage tool dependencies that involve python3?
If I let Galaxy install conda for me, it creates an environment with
python2, then if there is a too
