-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
2 possible package resolutions #76
Comments
Interesting -- the command run was specifically to update Great Expectations? |
No, I was doing:
And every time I run that command it switches from one resolution way to the other one. If I remove great-expections the update all command works without any issue. |
Warnings shouldn't be an issue. This just shows you that the solving algorithm of conda has found two solutions that are equal to its cost measures. Did you get an actual error? |
My problem is that every few days I run the command Right now every time I run that command, I don't know whether to consider it an error or not, but it is certainly not a desired behavior nor does it happen with the rest of the installed packages. |
I think the problem is with dependency In version 0.7.11 of While in recent versions of I think that the problem is that in one execution conda updates The question would be if actually |
@juanfcocontreras I just created this PR: great-expectations/great_expectations#2020 to try to update our version requirements. As I recall, the issue with requests 2.24 was actually caused by an incompatibility with the snowflake driver for SQL. For users not using that driver, I suspect using 2.24 would be fine. See: great-expectations/great_expectations#1623. I don't know whether snowflake has addressed the issue: snowflakedb/snowflake-connector-python#324 |
Great! Thank you! |
It seems that the PR has some issues. Could you check it, @jcampbell ? Thanks in advance! |
Since the last update, I have a conflict to update:
The text was updated successfully, but these errors were encountered: