-
-
Notifications
You must be signed in to change notification settings - Fork 267
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
Running "python -m pip check" in every Python package #962
Comments
@CJ-Wright @beckermr, what do you think? Is there a way to automatically add this to recipes? |
We need three things:
|
Do you know since which version pip has this feature? |
One of the example where this recently popped up: conda-forge/watchdog-feedstock#14 (it broke conda-forge/dagster-feedstock#8) |
It was added in |
I would structure this as a mini migratior so it can run piggy back on the main migratiors. |
This would be great to have, but only for packages that use pip |
This check is also working for Python packages that are installed without |
@xhochy - I guess I am ignorant here, then. How does it work? |
It retrieves the current |
Related: regro/cf-scripts#519 |
Alright, we have a piggybakc migrator going for this. It will slowly creep into the feedstocks. |
Now that we have automerge support and that the newer
pip
versions supportpip check
to check for a consistent environment, should we add this as a test to all Python packages?I have added it to some packages and I see it failing quite often as downstream miss dependency updates when they do version updates.
Todos:
The text was updated successfully, but these errors were encountered: