-
-
Notifications
You must be signed in to change notification settings - Fork 450
Define default extra env configured to auto-activate
#740
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
Open
jaimergp
wants to merge
33
commits into
conda-forge:main
Choose a base branch
from
jaimergp:default-env-experiments
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
default extra env configured to auto-activate
3 tasks
This was referenced Apr 24, 2025
…ge; branch 'main' of github.com:conda-forge/miniforge into default-env-experiments
This comment was marked as resolved.
This comment was marked as resolved.
3 tasks
Member
Author
|
Tested locally and works as expected. |
default extra env configured to auto-activatedefault extra env configured to auto-activate
hmaarrfk
reviewed
Jul 18, 2025
hmaarrfk
reviewed
Jul 18, 2025
Contributor
|
i'm not sure if this will "help" or add more confusion. I need to think about it. |
Member
Author
|
Oops the new constructor 3.12.0 is broken. Submitting: conda-forge/admin-requests#1586 |
19 tasks
Contributor
|
i think we should just bite the bullet and really start to provide better customization options for the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #636.
This is the setup:
baseonly holdsconda,mambaand their dependencies.default-envhas the same Python as inbase, but nothing else.default-envis now the default auto-activated environment which users can install things to.Note: This PR does not freeze
baseby addingconda-meta/frozen. That would be too disruptive for lots of infra conda-forge relies on (because we use these installers in many places), where we modifybasevery often. That work will be deferred to further efforts. OTOH, changing the default environment might disrupt CI workflows too (e.g. a blindconda update condawill fail becausecondais not ondefault-env).