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

ENH: Question on specifying specific conda environment #1343

Open
adam2392 opened this issue Sep 12, 2023 · 1 comment
Open

ENH: Question on specifying specific conda environment #1343

adam2392 opened this issue Sep 12, 2023 · 1 comment

Comments

@adam2392
Copy link

I have a Mac M1 setup, where I essentially have 2 conda environments: one from miniconda, which runs x64 and one from miniforge, which runs on arm64 (i.e. M1 chip). I want to run a benchmark comparing the current branch w/ the main branch. E.g. a command like this:

asv continuous --verbose --split --bench RandomForest origin/main constantsv2

My Python project is running on the miniforge environment (i.e.) the /Users/adam2392/miniforge3/envs/sktree environment.
However, whenever I run asv benchmarks, I get a compiler error. I think this is because the default conda environment is my miniconda env. I'm wondering how we can specify the conda environment to use when setting up the two environments for asv.

Here is my conda env list:

base                  *  /Users/adam2392/miniconda3
sktest                   /Users/adam2392/miniconda3/envs/sktest
                         /Users/adam2392/miniforge3
                         /Users/adam2392/miniforge3/envs/sktree
                         /opt/miniconda3
                         /opt/miniconda3/envs/sickkids

I'm following this page: https://asv.readthedocs.io/en/stable/env_vars.html and am not exactly sure what should be set. I'm wondering if it is possible / good to add a few examples of setting these environment variables and their consequences?

@HaoZeke
Copy link
Member

HaoZeke commented Sep 16, 2023

The environment variables are set, not read OTOH. I don't think this issue was considered during the design at all (I didn't think of it when writing the micromamba plugin) and it would probably need more design. As a workaround, what about locally setting the right PATH variables to find the correct environment?

@HaoZeke HaoZeke changed the title Question on specifying specific conda environment ENH: Question on specifying specific conda environment Sep 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants