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

Add note about channel_priority=strict to docs #28

Open
tlambert03 opened this issue Jan 24, 2021 · 1 comment
Open

Add note about channel_priority=strict to docs #28

tlambert03 opened this issue Jan 24, 2021 · 1 comment

Comments

@tlambert03
Copy link

Thanks again for your efforts on #25 and #27 ... I was able to build the environment on both mac and linux. however, it didn't work at first, and it was only after a while that I figured out the problem was the channel_priority=strict setting in my conda config. Since that is both the recommended setting from conda (will be default in 5.0), and since it is encouraged in the conda-forge install, I suspect that many of your users will probably have that config set. I tried for a while to get a working environment.yml even with that setting (by prepending each dependency with a specific channel), but I never succeeded. So, you may want to add a note to your install instructions that users should temporarily disabled channel_priorty=strict

@jburel
Copy link
Member

jburel commented Jan 24, 2021

Thanks for the heads up
I have it off by default. I will add a note.
I hope not to have to juggle between the various ilastik conda channels when we upgrade to the latest. Notebooks/scripts are still not working due to a problem with ilastik itself.

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