Open hehouts opened 1 year ago
This is the binder repo, I will not make any changes until its safe :D https://github.com/hehouts/lab14_binder
this is the binder launch link Ive been using: https://mybinder.org/v2/gh/hehouts/lab14_binder.git/HEAD/?urlpath=rstudio
some oddities 😁
/srv/conda/envs/notebook/bin/
is put in the PATH regardless of what conda environment you're in.
`/srv/conda/envs/notebook/bin/python -V' is Python 3.7.12
default Python in base
environment is /srv/conda/bin/python, /srv/conda/bin/python -V
shows Python 3.10.9.
yay.
HI there - i have the same error when trying to install in on a SLURM cluster using conda
(sourmash) [XXX@hpclogin01 ~]$ pip show sourmash Name: sourmash Version: 3.3.0 Summary: tools for comparing DNA sequences with MinHash sketches Home-page: https://github.com/dib-lab/sourmash Author: C. Titus Brown Author-email: titus@idyll.org License: BSD 3-clause Location: /home/XXX/miniconda3/envs/sourmash/lib/python3.7/site-packages Requires: cffi, deprecation, matplotlib, numpy, scipy, screed Required-by
so... is there a solution?
yep - looks like the solution is to make sure that python >= 3.8. As you can see @sapuizait yours is python 3.7 -
Location: /home/XXX/miniconda3/envs/sourmash/lib/python3.7/site-packages
let us know if that works!
yay! seems to be working!
Food for thought: should we change the conda install instructions from
conda install -c conda-forge -c bioconda sourmash
to
conda install -c conda-forge sourmash-minimal
?
We sort of kept the bioconda
package because it generates biocontainers, but otherwise it ends up causing compatibility problems if bioconda
is not set up in the recommended way...
(or, more extremely, we could rename sourmash-minimal
to sourmash
in conda-forge
and explicitly depend on conda-forge::sourmash
in the bioconda
recipe, but I think that might be too much confusion...)
This is a symptom of not specifying the version of sourmash you want to install. Newer versions are not compatible with Python 3.7 which means the installer looks for previous versions which are compatible and they find sourmash version 3.3.0. And this release is apparently buggy.
A solution would be to specify a recent version of sourmash in the docs. e.g.
conda install -c conda-forge -c bioconda sourmash=4.7.0
This will tell the user that is not possible to resolve the dependencies if it is run in a conda environment using Python versions < 3.8
This is a symptom of not specifying the version of sourmash you want to install. Newer versions are not compatible with Python 3.7 which means the installer looks for previous versions which are compatible and they find sourmash version 3.3.0. And this release is apparently buggy.
right, two issues here -
A solution would be to specify a recent version of sourmash in the docs. e.g.
conda install -c conda-forge -c bioconda sourmash=4.7.0
This will tell the user that is not possible to resolve the dependencies if it is run in a conda environment using Python versions < 3.8
yep. I'd like to avoid having sourmash version numbers hardcoded in the docs too much, because we always forget to update them, but it might also be something we can put into the release procedure.
I am not sure if this would have the desired effect, but you could try and release a new build restricintg the Python versions for older versions of sourmash. See: https://conda-forge.org/docs/maintainer/updating_pkgs.html#updating-recipes
our default binder/environment.yml in the sourmash repo installs python 3.10 and sourmash 4.8.2 without any version spec, so that's good, I think. not sure if binder updated the default python version or what.
(you can run binder from here, for example)
Hello!
I am trying to set up a binder using sourmash, and I am getting the following error:
if I run
pip show sourmash
in the binder terminal, I getcc: @luizirber , @ctb