8000 Installing from an explicit file into an existing environment should prompt the user to merge or replace the environment · Issue #14867 · conda/conda · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Installing from an explicit file into an existing environment should prompt the user to merge or replace the environment #14867

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
2 tasks done
jjhelmus opened this issue May 21, 2025 · 0 comments
Labels
source::contributor created by a frequent contributor type::feature request for a new feature or capability

Comments

@jjhelmus
Copy link
Contributor

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

When installing from an explicit (.txt) file into an existing environment, conda should ask the user if they want to replace the existing environment with the packages from the file or merge the existing environment with those in the file.

Why is this needed?

Installing from an explicit environment into an existing environment can result in an inconsistent environment.

What should happen?

When installing from an explicit (.txt) file into an existing environment, conda will replace any existing packages of the same name as the explicit packages without performing a solve. This can results in an inconsistent environment.

Rather conda should prompt the user when installing from an explicit file into an existing environment to determine if the intent is to replace the environment (e.g. delete and the create from the explicit file) or merge the existing environment (the current behavior). In the majority of cases the user likely wants the replace option.

Additional Context

No response

@jjhelmus jjhelmus added the type::feature request for a new feature or capability label May 21, 2025
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning May 21, 2025
@travishathaway travishathaway added the source::contributor created by a frequent contributor label May 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
source::contributor created by a frequent contributor type::feature request for a new feature or capability
Projects
Status: TODO 📬
Status: 🆕 New
Development

No branches or pull requests

2 participants
0