You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment snakemake is installed in its own mamba env when making a prodenv which is then used by each of the production cycles. Instead we could move to snakemake being in its own venv so different prod cycles can use different snakemake versions and extra packages can be installed such as pylegendmeta for snakemake to use outside the container. This could be handled by a modern package handler like uv (which would also handle the venv) thoughts @gipert ?
At the moment snakemake is installed in its own mamba env when making a prodenv which is then used by each of the production cycles. Instead we could move to snakemake being in its own venv so different prod cycles can use different snakemake versions and extra packages can be installed such as pylegendmeta for snakemake to use outside the container. This could be handled by a modern package handler like uv (which would also handle the venv) thoughts @gipert ?
@Yuan-Ru-Lin
The text was updated successfully, but these errors were encountered: