-
Notifications
You must be signed in to change notification settings - Fork 25
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
Conda update flips between two versions of the same package from the same channel #475
Comments
Hi @sam-s, Thanks for linking to the SO question. I read through it and noticed that setting Otherwise, rather than trying to force everything in your base environment to be at its latest version, I would recommend creating a separate named environment to use packages at their latest version. The base environment should really only hold the conda installation and its dependencies. For project specific work, we always recommend creating separate named environments for this purpose. You can find more information about managing conda environments in our documentation: Let us know if you have any further questions. |
Hi @travishathaway ,
Absolutely not. Both the linked SO and this issue clearly state
I am not. I have an environment in which I work which is not relevant to the question, and I have the base.
I never installed anything myself in
This is the question I have:
|
I'm observing a similar flipping behavior for these packages, I'm using
and then immediately:
|
Transferred over to |
Hi there, thank you for your contribution! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment. Thanks! |
Checklist
What happened?
With both
channel_priority: flexible
andchannel_priority: strict
,every
conda update -n base --all
flips betweenand
and the corresponding
conda list -n base --show-channel-urls
areand
where
XXX
is the exact same (internal/corp) channel (which I do not cotrol).My original report.
Conda Info
Conda Config
Conda list
Additional Context
No response
The text was updated successfully, but these errors were encountered: