Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: "environment_type": "mamba" fails #1353

Closed
jmccreight opened this issue Dec 8, 2023 · 6 comments · Fixed by #1372
Closed

BUG: "environment_type": "mamba" fails #1353

jmccreight opened this issue Dec 8, 2023 · 6 comments · Fixed by #1372
Labels
bug Triaged as a bug that needs fixing
Milestone

Comments

@jmccreight
Copy link

jmccreight commented Dec 8, 2023

On both MacOs and Windows, I'm unable to use mamba (which is problematic since conda is timing out when run in asv on windows). On both I get the same error

* Unknown environment type 'mamba'
* No environments selected

pip show indicates that I'm up-to-date with asv 0.6.1.

Maybe I'm missing something in my setup, but I've looked through the documentation as much as I can and dont see anything I find as germane.

Thanks for your help.

@HaoZeke
Copy link
Member

HaoZeke commented Jan 7, 2024

Is libmamba present? Could you provide some more information about how the rest of the environment is populated?

@jmccreight
Copy link
Author

jmccreight commented Jan 8, 2024 via email

@jmccreight
Copy link
Author

Hi again,

I think the simple solution is just conda install libmambapy in the environment with asv. Seems obvious. But I had to understand more on the relationship of conda and mamba to before I knew what to do.

I think that saying (in the installation instructions) that:

is kind of misleading because, at least as far as I could tell, while libmamba and libmambapy are available in the base env, you can not (easily) access them for other environments. I also did not want to install asv into base (which is forbidden by mamba). I was getting hung up on expecting libmamba to be available like conda is, from any environment. But maybe I missed another option here? As far as my solution is concerned, its irrelevant that these ship with mamba because you need a separate installation anyway.

Of course, libmambapy is not on pip and so cant be included in the pyproject.toml as an optional dependency either.

I'm still curious, how do you suggest making libmambapy available in non-base environments when using mamba? And I think it could be very helpful to mention this in the docs in one or two sentences.

Thanks!

@maximlt
Copy link

maximlt commented Jan 18, 2024

Have you tried running conda with the conda-libmamba-solver, instead of mamba? This is now the new conda default solver.

@trexfeathers
Copy link

Have you tried running conda with the conda-libmamba-solver, instead of mamba? This is now the new conda default solver.

For me, this has been fine. However I'm aware that Mamba does still offer other benefits such as parallel downloads.

@maximlt
Copy link

maximlt commented Jan 18, 2024

conda performs parallel downloads since end of 2022 :) https://docs.conda.io/projects/conda/en/stable/release-notes.html#id69

@HaoZeke HaoZeke changed the title "environment_type": "mamba" fails BUG: "environment_type": "mamba" fails Jan 27, 2024
@HaoZeke HaoZeke added the bug Triaged as a bug that needs fixing label Jan 27, 2024
@HaoZeke HaoZeke added this to the 0.6.2 milestone Jan 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Triaged as a bug that needs fixing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants