这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@kalefranz
Copy link
Contributor

@kalefranz kalefranz commented Sep 3, 2018

resolves #7656
supersedes #7660

$ conda config --describe channel_priority
# # channel_priority (ChannelPriority)
# #   Accepts values of 'strict', 'flexible', and 'disabled'. The default
# #   value is 'flexible'. With strict channel priority packages in lower
# #   priority channels are not considered if a package with the same name
# #   appears in a higher priority channel. With flexible channel priority,
# #   the solver may reach into lower priority channels to fulfill
# #   dependencies, rather than raising an unsatisfiable error. With channel
# #   priority disabled, package version takes precedence, and the
# #   configured priority of channels is used only to break ties. In
# #   previous versions of conda, this parameter was configured as either
# #   True or  False. True is now an alias to 'flexible'.
# #
# channel_priority: flexible

Signed-off-by: Kale Franz <kfranz@continuum.io>
Signed-off-by: Kale Franz <kfranz@continuum.io>
@kalefranz kalefranz requested a review from a team as a code owner September 3, 2018 21:59
Signed-off-by: Kale Franz <kfranz@continuum.io>
Signed-off-by: Kale Franz <kfranz@continuum.io>
@kalefranz kalefranz added this to the 4.6.0 milestone Sep 4, 2018
Signed-off-by: Kale Franz <kfranz@continuum.io>
@kalefranz kalefranz force-pushed the strict_channel_priority-3 branch from 4b31d1d to 7f4b5d8 Compare September 4, 2018 07:16
@kalefranz kalefranz changed the title strict channel priority strict channel priority via 'channel_priority' config option or --strict-channel-priority CLI flag Sep 4, 2018
…pveyor

Signed-off-by: Kale Franz <kfranz@continuum.io>
Signed-off-by: Kale Franz <kfranz@continuum.io>
assert stderr == ''
self.assertIsInstance(stdout, str)

def test_anaconda_solve_time(self):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Such performance/benchmarking tests are no bad idea, generally. Especially in light of all those index and solver changes for 4.6.x.
It could make sense to add a @pytest.mark. to those and only run them on demand and/or in a separate, e.g., nightly, job. Or, if necessary, even put them into a separate test suite or repository.
I'd probably just use some @pytest.mark.performance and/or create a test_performance.py and set

import pytest
pytestmark = pytest.mark.performance

in there.

@ocefpaf
Copy link

ocefpaf commented Feb 11, 2019

@kalefranz and @mbargull just wanted to let you know that, even though it took me a while to test this, so far it has done wonders to our workflow! Thanks a lot for implementing this!

@msarahan
Copy link
Contributor

Glad to hear it! Hopefully it doesn't have any nasty side effects and we can make it the default someday soon.

@kalefranz
Copy link
Contributor Author

I'll add the default value change to #7394

@ocefpaf
Copy link

ocefpaf commented Feb 11, 2019

Glad to hear it! Hopefully it doesn't have any nasty side effects and we can make it the default someday soon.

So far everything is working as expected, even the failures 😄

I'll make sure to report anything unexpected.

@github-actions
Copy link

Hi there, thank you for your contribution to Conda!

This pull request has been automatically locked since it has not had recent activity after it was closed.

Please open a new issue or pull request if needed.

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Aug 29, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

locked [bot] locked due to inactivity

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"strict" channel preference

4 participants