-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Chardet run constraint should be normal constraint #55
Comments
Ok, the new build However, it's not trivial to downgrade an existing repo. I had to do the following:
If you don't provide the exact build number, the solver will not downgrade chardet from 5.0.0 to 4.0.0, so you won't actually get the fixed build. |
run-constrained is the correct solution in general here because chardet is not an actual dep, it is an optional dep. If we list it under run or deps, then it would be installed always which is not needed. The problem with the solver is a separate issue, but I think they have listed the build as broken here conda-forge/admin-requests#452 (we could have done another retroactive run-constrained actually, but oh well) |
which is correct. |
Yes, it is correct, but as I maybe didn't explain sufficiently, the solver, at least mamba, seems to not notice that the build 0 is marked as broken. Hence it is kept, and not updated to build 1 - maybe because upgrading to build 1 would mean chardet would have to be downgraded. One could check with conda, but I don't use conda anymore. My problem was with an existing environment, that already had build 0 installed and failed to upgrade to build 1. |
Ah! Makes sense, sorry... |
Issue
I've installed the latest requests build from conda-froge.
I now always get the following warning:
The root cause seems to be this commit from two days ago:
4d7cfb9
I don't understand why this is set as a
run-constraint
and not as a normal constraint. If it was a normal constraint, then conda would install an appropriate chardet. But now this is not the case.The text was updated successfully, but these errors were encountered: